posted 02-28- 09:56 AM               

Having some trouble with folks getting CTDs on the beta version of the Corsair, particularly in Glide mode. Kinda problematic for me, since it works good on my machine in D3D, and not at all in Glide, which leaves me no way to check and correct it

Razer mentioned you have a debugging program of some kind for .sm files. Any chance of you running the f4u1.sm file through it, or alternatively me getting a copy of the program? I understand if you don't have time for this, and I've got a (tedious) "fall-back plan," but if you can find any obvious problems, it would sure help me out Thanks,

posted 02-29- 10:40 AM               

If you do have time, and find something serious, I'd certainly appreciate it, but I guess if you did it for me, it would probably open the door for a lot more "troubleshooting" than you probably want to do, or have time for.

And doing it for one plane and not the others wouldn't really be fair either, on reflection.

So I guess let's not worry about this for now. If the plane becomes unusable somehow I might repeat the request. (Maybe hold off until after the contest--planes that "work" should have an advantage over those that don't I would say).

posted 02-29- 03:03 PM               

bear in mind that once you've uploaded a file, you won't see it displayed. As long as you don't get any errors, you can rest assured that the file is there.