Error message concerning progdefs.h being out of date...
Error message concerning progdefs.h being out of date...
Quake crashes with:
"progs.dat system vars have been modified, progdefs.h is out of date"
i'm trying to add new items so i think that may be what's causing it, but i can't figure out exactly what it means...
progdefs.h gets made everytime i compile the code so i don't understand how it can be out of date...
help?
"progs.dat system vars have been modified, progdefs.h is out of date"
i'm trying to add new items so i think that may be what's causing it, but i can't figure out exactly what it means...
progdefs.h gets made everytime i compile the code so i don't understand how it can be out of date...
help?
Usually this happens when you add or change stuff too high in defs.qc. If you added any globals, variables, etc, make sure you move them to below the area where it defines:
void end_sys_fields; // flag for structure dumping
void end_sys_fields; // flag for structure dumping
When my computer inevitably explodes and kills me, my cat inherits everything I own. He may be the only one capable of continuing my work.
DON'T CHANGE THE TOP OF DEFS.QC!!!!
I'm warning you...
Well, yeah, it tends to come up with a message...
Something about progdefs.h being out of date.
Oh, err, yeah, what Wazat said.
Technical stuph. QCC (which ever one) generates a progdefs.h file when compiling. It builds this file from the defs above the void end_sys_fields; definition.
The engine was compiled with a copy of this .h file generated by id.
If they don't match up, the engine will refuse the progs. You can look inside it to see the differences and which changes you need to undo to get it working again.
I'm warning you...
Well, yeah, it tends to come up with a message...
Something about progdefs.h being out of date.
Oh, err, yeah, what Wazat said.
Technical stuph. QCC (which ever one) generates a progdefs.h file when compiling. It builds this file from the defs above the void end_sys_fields; definition.
The engine was compiled with a copy of this .h file generated by id.
If they don't match up, the engine will refuse the progs. You can look inside it to see the differences and which changes you need to undo to get it working again.
-
- InsideQC Staff
- Posts: 1120
- Joined: Sat Oct 16, 2004 3:34 pm
sorry, forgot to post that i found the problem. i was using items2 for the hipnotic icons but put it below items, which was above that line that you guys said not to put anything above. ^_^
anyway, thanks for the help, guys.
also, frikac, you're saying that if i added a parm17, it would be treated as just a normal float, and not carry over to different levels?
anyway, thanks for the help, guys.
also, frikac, you're saying that if i added a parm17, it would be treated as just a normal float, and not carry over to different levels?
yeah, i figured that out already. what i meant was if i added a parm17 later on down the line.If you added a parm17, it would be the same as adding anything else to the 'special' list... you'd screw it up. You'll notice that when you compile, QCC generates a file called 'progdefs.h', which contains globalvars_t and entvars_t, C structures based on what is defined above the dumping flags in QC. The Quake engine compiles with progdefs.h, so if you change what's in it, it won't match the engine any more.
also, i too agree that the reply button is small and annoying to click on... can we have a nice 'Reply' button at the bottom where it makes the most sense? ^_^