LÖVE 0.7.0 Game Slave released

[pygy]

Also: w0000000t!!!

[com_1]

! WARNING !
-----------
This software is not complete. This is just a preview. Don't expect to find any
interface consistencies between releases at all. With each release, everything
you once knew and loved may be brutally murdered. By which I mean removed and/or
changed.

Now I understand why not working.
I'd rather wait for "LÖVE 0.7.0" a stable version.

[nevon]

! WARNING !
-----------
This software is not complete. This is just a preview. Don't expect to find any
interface consistencies between releases at all. With each release, everything
you once knew and loved may be brutally murdered. By which I mean removed and/or
changed.

Now I understand why not working.
I'd rather wait for "LÖVE 0.7.0" a stable version.

0.7.0 is stable. There's just no guaranteed API stability between versions. Meaning games written for 0.7.0 may not run in 0.8.0.

[bartbes]

0.7.0 is just as stable (hopefully more stable) than 0.6.2, what it means is that we haven't reached 1.0.0 yet.

[Endeg]

Good day, fellow lovers

0.7.0 crashes on my computer and won't crash on anything else. At first, I thought it might be some msvcr80.dll nonsense or some fancy framebuffer thing, but Dependency Walker showed me this:

Second chance exception 0xC000001D (Illegal Instruction) occurred in "LOVE.EXE" at address 0x004401C1.

I guess it means that my processor is too old-school for new version of Love or compiler used for this build. Is there any way to make it more retro-friendly?

[bartbes]

Since you seem to be convinced it's your cpu, what cpu do you use?

[TechnoCat]

Good day, fellow lovers

0.7.0 crashes on my computer and won't crash on anything else. At first, I thought it might be some msvcr80.dll nonsense or some fancy framebuffer thing, but Dependency Walker showed me this:

Second chance exception 0xC000001D (Illegal Instruction) occurred in "LOVE.EXE" at address 0x004401C1.

I guess it means that my processor is too old-school for new version of Love or compiler used for this build. Is there any way to make it more retro-friendly?

Aw man, deep down i knew SSE2 was a bad idea. I can try recompiling without that for you.

What CPU do you have?

[Endeg]

Since you seem to be convinced it's your cpu, what cpu do you use?

Aw man, deep down i knew SSE2 was a bad idea. I can try recompiling without that for you.

What CPU do you have?

It's Athlon XP, and yes, it doesn't support sse2.
The recompiling would be just great .

[TechnoCat]

It's Athlon XP, and yes, it doesn't support sse2.
The recompiling would be just great .

Here is an SSE build for Windows. The purpose of this is to support old CPU's.

[Endeg]

It's working! Thanks