Clicky.
Two points to note.
No fog. Built-in fog is no longer available on Shader Model 3+ hardware, so if you want to have fog that works on all cards you need to write your own fog code in shaders. Yes, that sucks mightily, but I am not the one making these decisions. In the end I decided to just remove it rather than have it working on some and not working on others.
"But OpenGL fog still works!" I hear you cry. Yes, but that's because every OpenGL implementation is required to implement the full specification, and fog is still in the full specification. An OpenGL implementation however has complete freedom with regard to how it implements the specification. So what you are seeing is most likely a software-based implementation of fog. Direct3D is a lot more unforgiving - it exposes the bare bones of what's supported on the hardware and nothing more. No software fallbacks (except one very odd one in supporting vertex shaders in software), no get out of jail free clause.
Yes, it still sucks. For 1.9.0 I'm intending to use vertex shaders on everything (using that software implementation if you don't have the hardware) and we'll get fog back then. Promise. For now rather than make a mess, and rather than explain why a feature works for some but not for others, I decided to not have that feature at all.
Second point is that if you get any errors or crashes with this release your first thing to do is upgrade your DirectX. Always always always. Even Windows 7 comes with a downlevel version of D3D9, so upgrade it. If it still crashes then tell me how to reproduce the crash.
This has been tested on a variety of Intel and NVIDIA hardware, on Windows 2000, XP and 7, and with various different versions of D3D9, but the objective is to remove unknown factors so that we can focus in on known ones. So upgrade.
Wednesday, April 14, 2010
Release 1.8.3 is now available
Posted by
mhquake
at
6:29 PM
Subscribe to:
Post Comments (Atom)
9 comments:
Yay! Will test it straight away :D
the instruction at 0x004240fc referenced memory at 0x00000000. The memory could not be read.
------------------------------------
I have 1.8 ghz dual core and
integraded intel 945 graphics card.
running Win7.
Fog appears to be broken for me :(
(it worked fine on 1.8.2 tho).
Same deal with crosshair-color, I guess we can have any color we like, as long as it's white ;)
On the bright side, it runs very smooth now, no fps drops, no stuttering, so great job on that! :D
Fog has been removed as it's no longer supported in hardware on SM3+ cards. Basically that means that if I want to do fog on all hardware I need to write my own fog code. :(
I assume that OpenGL fog is emulated in software, but D3D in unforgiving.
@gnounc - upgrade your DirectX first, then see if it happens again. Also, what were you doing when it happened? I've run this on an Intel 945 and it works fine.
Sorry for not being more specific. Uh, it crashes on start. Direct x is at directx 11.
Updated version does the same thing.
Ill install quake fresh and see if it does the same thing.
Still no go ..I dont think I'm doing anything stupid, I turned off spybot.
But have you upgraded your D3D9? If this is a fresh install of Windows 7 you have a downlevel version of D3D9 on it. Updates to D3D9 have been released since the release of both Vista and 7 that are not included on either Vista or 7.
You can safely update without affecting D3D11.
I remember you mentioning that a while back now.
Yessirrreeee that fixed it, thank you much.
That's a pint you owe me. :D
Post a Comment