Direct 3D 9.0c Quake

by **=peg=** » Fri Jan 23, 2009 3:05 am

I was just working on a lil and figured i'd try it in DirectQ 1.3.

to my surprise the lightmaps got totally messed up...

here is a screenshot of the map in glpro399:

and here is the same map in DirectQ 1.3:

this map is compiled with QuArK's ETP map format, using BJP's tools.. I don't know if that has anything to do with it but, i figured i'd report it for the same may happen on other maps..

(btw, don't mind the difference in brightness in the two screenies since i used pulsating lightstyles, they were always gonna be different. However do note the messed up light maps..)

by mh » Sun Jan 25, 2009 11:35 pm

File link's dead - you wouldn't mind reposting? I'd like to fix this one.

by mh » Mon Jan 26, 2009 12:09 am

by **=peg=** » Mon Jan 26, 2009 3:55 am

by **r00k** » Mon Jan 26, 2009 4:20 pm

by mh » Mon Jan 26, 2009 6:54 pm

Sorted.

r00k was spot on; I was missing a "this->AcceptsInput = true;" in the constructor - more differences between debug builds and release builds with the MS compiler, and it's not the first time I've seen that. :evil:

(What's the point in having a debug configuration if it's behaviour can't be guaranteed to accurately simulate the release configuration?)

Keyboard input is fully software by the way, and will likely remain that way, at least for a while.

by mh » Tue Jan 27, 2009 1:45 am

by mh » Wed Jan 28, 2009 1:38 am

by **=peg=** » Wed Jan 28, 2009 3:02 am

by mh » Wed Jan 28, 2009 1:20 pm

by **=peg=** » Thu Jan 29, 2009 4:27 am

by **MeTcHsteekle** » Thu Jan 29, 2009 11:06 am

by mh » Thu Jan 29, 2009 6:23 pm

by **Zzanitari** » Thu Jan 29, 2009 10:33 pm

I'd really like to test this out! But whenever I try to load this it comes up with W_LoadWadFile: couldn't load gfx.wad.

What do I do to fix this??

by **Baker** » Fri Jan 30, 2009 1:24 am

Direct 3D 9.0c Quake

Who is online