[Fry_Day]

The state of fsscp seems to be just getting worse - current CVS build, clean, crashes, logfile including "2d.h  - about to init 104". It tries to init an invalid display mode, making it call int3. int3 calls the display mode init with 0, to disable display, but since the display mode is illegal, it is an infinite loop that causes a stack overflow. suspect - launcher.

Edit: I changed my mind. crashes under OpenGL only

[Bobboau]

I've been getting odd graphics problems with debuging, any time it is suposed to minimize (warning/error/assert) or MSVC is suposed to regain focus (ie run to cursor) I just get a white screen, I've had to use the -window comand line and alt-tab to debug.

[phreak]

define USE_OPENGL

[Inquisitor]

I thought that the "run in a window" thing was fixed?

anywho, I clean built yesterday, and ran part of a user campaign, I got no errors like that, I am runing in d3d with the dx8 build.

and as for "things getting worse" you do realize that 1) we're in teh middle of bughunting and fixing, and 2) that's not a very nice way to put it.

fry: would you like ot join the project?

[Bobboau]

I think you would make a good addition

[Fry_Day]

I'm flattered, but, I'm on the verge of finishing high-school, and I'd rather do it with good grades

In a month, tops, I'm totally free of that. YAY!

Edit: On an unrelated note, I've installed SP5 and the processor pack for MSVC6, yet it doesn't detect the new registers in inline asm, and doesn't have the __m64 or __m128 data types. I wanted to red0 the vector lib with some sort of SIMD, but I find that quite a hindrance...

[Inquisitor]

Let me know when you get out of school.

Sounds like you have some Visual Studio funkiness going on though.

[Fry_Day]

Last test - June 26th. 'Nuff said


Edit - back to my MSVC woes - After doing everything imaginable, I can get MASM to do SSE stuff, but Visual C still refuses to recognize the types __m64 and __m128, and the inline assembler also refuses to recognize SSE-related commands. NGAAH!!!