TROR does this thing that you see sprites through the walls until you enter the TROR.
My MOD Is in HRP mode no polymer (for this mod).
Didn't do that with older Eduke32 (32 bit) I used before I got my new PC.
With new PC I use Eduke32_Win64 cus Duke32_32 wont work, TROR does this weird flashing hom.
Thing goes apeshit causing flashing hom in TROR if I use Eduke 32 bit on a 64 bit windows.
So Duke32_Win64 and or Duke64 works fine for me.
Only bug is the sprites being seen through walls from TRORs.
Bug vanishes when the room with the sprites cannot be seen or you're inside the TROR.
Page 1 of 1
TROR bug with Eduke64 and or the Eduke32_win64.7z file. "Weird TROR bug occurs with Eduke64 and Eduke32 for Windows with 64 bit"
#1 Posted 18 June 2014 - 06:19 PM
#2 Posted 19 June 2014 - 06:26 AM
So it happened when you switched to a different computer you say? I did warn you that in polymost, TROR can be glitch-free on some computers, but have nasty problems on others.
Whether this is the actual problem or not, I'd definitely test the maps on more than one computer to see whether they're glitch-free at various stages of development instead of risking a lot of wasted effort, or forcing a switch to polymer.
Whether this is the actual problem or not, I'd definitely test the maps on more than one computer to see whether they're glitch-free at various stages of development instead of risking a lot of wasted effort, or forcing a switch to polymer.
#3 Posted 19 June 2014 - 01:13 PM
Mickey C, on 19 June 2014 - 06:26 AM, said:
So it happened when you switched to a different computer you say? I did warn you that in polymost, TROR can be glitch-free on some computers, but have nasty problems on others.
Whether this is the actual problem or not, I'd definitely test the maps on more than one computer to see whether they're glitch-free at various stages of development instead of risking a lot of wasted effort, or forcing a switch to polymer.
Whether this is the actual problem or not, I'd definitely test the maps on more than one computer to see whether they're glitch-free at various stages of development instead of risking a lot of wasted effort, or forcing a switch to polymer.
I would switch to polymer but problem is my earlier level uses those "window thingie known as window glitch" that infamous bug exploit some users used to make "1 sided windows"
and they don't work on polymer they become "sky"
You know that thing Billy Boy used and other authors.
Those 1 sided windows Billy boy and I used a lot.
Share this topic:
Page 1 of 1