06-06-2014, 03:20 AM
(06-06-2014, 01:52 AM)eliot Wrote:I just sent you an email with Core.U and Engine.u(06-06-2014, 01:16 AM)TigerTiger Wrote: Hey Eliot, I love your tool. Do you happen to know the reason why UE Explorer won't decompile Vanguard (uses UE 2.5). I ask because I am trying to compile .U mods for the Vanguard Emulator. If I use UT2004 to compile a simple Hello World script Vanguard throws out some errors. It is worth pointing out that my simple Hello World script is correctly decompiled in UE Explorer which makes me believe Vanguard must do something slightly different then most UE 2.5 games. If I hex edit the memory of the running game to override an existing function with my "hello world" log function it works.
Error message with my script in Vanguard:
Critical: Bad import index
Error Message with Vanguard Scripts in UE Explorer:
Index was out of range
Its worth pointing out that if I try to load a file from UT2004 in Vanguard that has say 4 dependencies, the game will ask for each dependency and will not crash until all the dependencies are loaded.
1. I have not explicitly supported Vanguard. I know I said I won't support it although I can't remember why, nor do i have the core and engine.u files for it, feel free to send me.
2. It is high likely that the developers modified their version of the engine therefor UE Explorer doesn't understand it by default.
3. The developers probably kept the backward compatibility support in place so older packages can be loaded such as UT2004 but beware UT2004 has its own modifications to files as well but that depends on its content.
4. I'm guessing that bad import means one of the imports(dependencies) could not be found, I'm not sure why your tested packages worked and your own didn't but perhaps it may just be due limited backwards compatibility.
And to clarify I get the import errors in both the game and in UE Explorer because they are trying to read non existing import names for example -1234567 out of 5