-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serializing blueprints #9
Comments
There shouldn't really be anything in particular that prevents it from serializing blueprints. Although there are a few things that prevent it from being able to extract assets from any game except Fortnite. Usually when serializing a blueprint, it either works or it doesn't. When it doesn't work, it should print out an error message showing where it failed. Usually this is because of a structure or a property type that I haven't added support for. If you can show me the error message you're seeing, I may be able to add support for whatever is causing it. |
I have errors for whole file
Only two things were serialized correctly. |
I never was able to figure out the Is there anything in the resulting file that's missing that you are specifically after? It'd be quite a bit of work to get all of these classes supported. |
I want to find analog input functions or coefficients to repair movement that is tied to 30 FPS and is broken in 60 FPS (Arsenal is moving with half speed max and editing config file with binds can fix it, but then boosters angle is broken). So maybe FloatProperty and IntProperty is what I need. |
What confuses you about StructProperty? Ask your answers and sholl be granted. |
I was able to serialize FloatProperty and IntProperty correctly, but there isn't actually any useful information present there. At least, not in the structures beyond the default UObject. So basically, if nothing useful is showing up in the current serialization, adding these new serializers won't be useful. |
Yeah, Struct property is basically a proper StructElement or UObject. When talking about default UE4/Fortnite the Structs are all known so it just a matter of creating struct types map and checking if type of a Struct from asset file matches any in the map and parsing it, otherwise, just process it as generic UObject without padding. Issues may arise when:
|
Gonna close this now. Most of these structures seem pretty much useless, at least the ones I was able to serialize. |
Is it in plans to support serializing blueprints?
Thanks for your work. Your parser made translating Octopath Traveler much easier :D
The text was updated successfully, but these errors were encountered: