MTrop
[DecoHack] Not Compiling when it's reported to be successfully compiled
Not sure how to recreate this but I typod in my code and when I went to fix it, it said "compiled successfully" however it wasn't compiling it was using the old broken code. only after changing the thing definition to Thing 200 : Thing 22 "Mini Cyber" from Thing 200 "Mini Cyber" did it actually compile, afterwards I walked back the code to the previous version and it compiled successfully.
Without an example, I'm afraid I can't be much of a help on this issue.
When you say, "it wasn't compiling," did it not create a DeHackEd file, or did it create one without any additional data in it (blank sections)? Because unless some data was actually changed, it won't write anything to a file.
I had experienced this similar issue before, it will report that the code was compiled succesfully after pressing export, however it doesn't actually patches the wad with the new code I've written. I doubt it's something related to things, since I was trying to edit the chainsaw and had that happening. I also had that happening while editing other weapons
I have check a million times if I wasn't begin dumb and exporting to the wrong wad, however the path was correct. It also fixed itself after changing a bit of the code.
I need both the code (and maybe the output) of the patches in question or I will not be able to investigate this issue. Exporting to a WAD file from the GUI program currently works for me, including overwriting a patch that already exists.
Is the WAD file you are trying to write to already open by another program? If so, it may not write it successfully, but then again, it should error out if that's the case. Using a program like SLADE to keep a WAD open will allow writes to a WAD without actually updating its data when you go read it again, unless you re-open the WAD file.
Is the WAD file you are trying to write to already open by another program? If so, it may not write it successfully, but then again, it should error out if that's the case. Using a program like SLADE to keep a WAD open will allow writes to a WAD without actually updating its data when you go read it again, unless you re-open the WAD file.
I had SLADE open while making my patch, however it didn't still fixed the problem, and since you mentioned this, I had times where I forgot to close the game and clicked to export the patch, and it did not error out. It has only happened 10 or so times I think.
I need both the code (and maybe the output) of the patches in question or I will not be able to investigate this issue. Exporting to a WAD file from the GUI program currently works for me, including overwriting a patch that already exists.
Here you go, the output from decohack compiler is on the .txt file, looking into it, there's nothing other than warnings about integers getting converted to point-fixed numbers. Also besides the name of the decohack file, it's not using any ID24 stuff, I just never renamed the file after begin done with it.
Unfortunately, even with the provided code, I still cannot recreate this.
Tried compiling to a DEH. Works. Tried compiling and output into a new WAD. Works. Tried compiling via newest SLADE to recreate DEHACKED in the new WAD file. Works.
It seems impossible to recreate on my side - I'd have to catch it in in the act, but even with my personal projects, I haven't gotten this to happen once.
I'll keep the issue open, but I'll have to get outside help catching this bug.