Here's a strange one for you.

I enter "#define COLOUR_BLACK $000000" in my definition file. It returns -16. However, if I enter $000000 as a literal in the code, it comes out to 0 like it's supposed to. Every hex value I try to #define turns out this way -- $FFFFFF, which should be 16777215, comes out to 268435424. This is no huge deal since I can just #define the decimal values instead, but for the sake of readability it would be nice if it, um, worked.


Edit: I found something much weirder, though I'm not positive that I'm correct in its origins, and even if I'm right I can't offer any help in pinpointing it, which is why it gets tacked onto this post instead of put in a new one.

This is the insanest thing ever. Certain entities seem to be being spawned as not-obstructions where they were normally spawned as obstructions. I screwed with the code for a bit and found out that the problem only occurs when I have exactly this number of functions declared. Adding or removing one fixes everything, regardless of which one I add or remove. Adding or Adding or removing a #define, on the other hand, changes which entities are created as obstructions and which aren't. Adding or removing two #defines solves the problem.

Edit to the Edit: Actually, after adding a bunch more entityspawns to the map, it looks like adding more functions CAN cause the bug to crop up after a point. Exactly which entities have problems is definitely a function of the number of functions and defines, though.

I found yet another bug with File I/O.

FileSeekLine() messes up if you have any string in the file that is longer than 255 characters. If the string is over 255 characters, it treats the part over the 255 characters as a new line...

Quote:Originally posted by Gayo

I'm afraid that this isn't a very useful bug to report since I can't figure out what the hell the problem is, but...

I've got a struct. The struct contains a bunch of variables, one of which is a string. If I try to set the string, VERGE crashes with the generic useless Windows error. However, if I make the stuct's internal string part of a string array, everything works perfectly. I can't reproduce this error in a clean directory with nothing but the struct defined, and assigning values to lone strings seems to work for my other structs. Has anyone had anything like this happen?

Perhaps.

El

Nevermind this, I figured out a way around it.