Matty,
I have tested it on 2 machines. the First was a Vista PC and would not start at all (memory access violation) very likely something to do with whatever you load in at the beginning - I think there is a slight difference in the file system to vista that is not normally noticable, but I have seen it affect certain apps. It is definitely different from XP home, because it uses folder permissions properly.
When I tested on an XP machine, it loaded and began to play fine until I killed my first bad guy. Then I got the memory access violation again. Just IMO it was probably trying to play a sound it failed to load or was looking for a variable that was missing (i.e. a custom type not declare properly).
Hope this helps.
I would recommend using some flags when loading things such as sounds, models, textures, images etc, as you can use them in your code to determine what failed to load and report that to a log file or close with an error message explaining what went wrong. I often implement this idea early on in my programs, saves a lot of time and head scratching when things go wrong.
.... But I like it so far. :)
I have tested it on 2 machines. the First was a Vista PC and would not start at all (memory access violation) very likely something to do with whatever you load in at the beginning - I think there is a slight difference in the file system to vista that is not normally noticable, but I have seen it affect certain apps. It is definitely different from XP home, because it uses folder permissions properly.
When I tested on an XP machine, it loaded and began to play fine until I killed my first bad guy. Then I got the memory access violation again. Just IMO it was probably trying to play a sound it failed to load or was looking for a variable that was missing (i.e. a custom type not declare properly).
Hope this helps.
I would recommend using some flags when loading things such as sounds, models, textures, images etc, as you can use them in your code to determine what failed to load and report that to a log file or close with an error message explaining what went wrong. I often implement this idea early on in my programs, saves a lot of time and head scratching when things go wrong.
.... But I like it so far. :)