.qc (dot qc) - the group for quake c coders of all denominations. If you make quake one mods and write code in quake c, join our group! I'll try to answer any quake c questions - please post your inquiry in the forums...
Posts | ||
---|---|---|
Compile error - unknown value | Locked | |
Thread Options | ||
|
Feb 20 2017 Anchor | |
This happened: I was testing various modules. X monsters are not on the compile list now as I have yet to Code fragment:
This is a considerable concern. "framerloop" is one of my new macros to replace But - how did this fail compile? I have 65 of these that compile every time with no problem. And I just compiled this a few minutes back with no issue. I played with this a bit. I could find no reason heximp_sit1 is unknown.
As often happens when using 3 or 4 different interface (scite, geany, vi, bash term line, web stuff like this) So, the case seems that a stray char before a macro can cause bizarre results. Sometimes it pays to fix errors in order of appearance rather than focusing on the most important. When I removed the stray "f", the module compiled fine. |
Only registered members can share their thoughts. So come on! Join the community today (totally free - or sign in with your social account on the right) and join in the conversation.