xtbl editing crashes since new patch!

ok. i understand some xtbls need to be edited under notepad ++ or the xtbl editor. problem is, weapons_upgrades.xtbl worked fine editing til this new patch. >.< and i tried editing it everywhere else. buut guess what happens? crash! and i KNOW its this particular xtbl that crashes it. because whenever i remove it, everything worked just fine. but every time i try editing the one from the patch: crash! any help here would be juuust great.
trying to remove the overheat limits on each alien weapon. which worked great.... til this patch again starts wiping upgrades of certain weapons.

and yes. i tried the one from the patch. thats what caused the crashing
 
Last edited:
Did you try to extract just the xtbl and not change anything. If you put the one the game is actually reading(most likely in a patch packfile) then the game will not crash when reading it. If you get an older one like from the original shipped packfile it could crash. I would do it without changing anything first because then you know if it is the correct file.
 
thats exactly my problem. i got the weapons upgrade xtbl FROM the recent patch. and if i change the overheat info to zero the game crashes. ill test this with the unedited patched file.
confirmed. the xtbl from patch_compressed vpp causes the crash itself. >.<
 
Last edited:
That tells me that it isn't the file that is actually read...or something is wrong with the extraction. Can you attach the xtbl you extracted?
 
ok here. i extracted it with thomas jepps saints row tools revision 12.....
im pretty sure it IS the file being read. seeing how the misc tables.vpp remains unchanged since the games launch wheres the PATCH was changed december 10th when the update happened.
 

Attachments

There is something wrong with that xml file. Around like 261 it looks like it ends and then just keeps going. Our parser explodes on line 265. I'm not sure what is broken here, but that doesn't seem like the xml file we would read. Our table file seems to be about 283k or so.
 
There is something wrong with that xml file. Around like 261 it looks like it ends and then just keeps going. Our parser explodes on line 265. I'm not sure what is broken here, but that doesn't seem like the xml file we would read. Our table file seems to be about 283k or so.
well crap. so the update broke it? :<
wasnt like that before the patch.
edit: AHHHAAAAAAA!!!!!
i figured out what i did wrong. i used an outdated extractor!
NOW everything works perfectly
thanks so much for taking time out to help me with this. >.<
 
Last edited:
Back
Top