   Advanced shader demo with physics, looking for framerate results
  I've been working on an engine off and on for the past year and decided it is time to gather some framerate results. The shader portion of the engine has had little optimization so dont be shocked if you have a low framerate. The demo contains per-pixel point lighting with self-shadowing bump maps and specular intensity. I will be adding soft/hard shadows tonight using shadow mapping and plan on adding parallax or hopefully relief mapping by the end of next week. I want to prepare you for the crappy modeling. I modeled the room myself so of course it looks like crap but it gets to the point. If you're an artist looking to join up with me please don't hesitate to contact me.The demo requires a video card that supports pixel shader 2.0 and has at least 64megs of video memory (hopefully you have more). It also requires you to have the latest DirectX. Click here to download DirectX 9.0c.I forgot to mention the controls. You should know the movement controls and use space to throw a sphere.Thank you,Jonathon Davisjonathon7989@hotmail.comAIM: Legend768[Edited by - jdavis on June 4, 2006 5:31:12 PM]
  Your demo looks and behaves very cool! Did you write the physics yourself? Though sometimes the screen becomes completely black when all lights move to the other side of the room.Specs:proc: Athlon XP64 3200memory:    1024 MBvideo:GeForce 7900framerate: +- 120   ;  Do I spy the Magdalena model by SkullBox there? Which version is it, the Q3, or the UT2k..?   ;  "The application failed to start because d3dx9_25.dll was not found".DxDiag reports that I've got version 9.0c of DX installed.   ;  It ran dirt slow on my machine (only 45fps) [oh]I suspect one of the reasons for the sluggishness was that the app was CPU bound (my cpu isn't exactly very fast [smile])Also the shading was a lot brighter than that of your screenshots and the lights flickered in an almost epilectic-fit-inducing manner [wink]PC Specscpu: Sempron 2800+gpu: Geforce 6600gtram: 512mbfps: ~45fps   ;  That's because MS are idiots :-)At first, the D3DX library was in the same DLL file as D3D. When D3DX got bigger and more bloated (one has to decide if it's for the better), MS wanted to separate it to a different component. They did this as of the Feb 2005 release of the DX SDK. They claim to want to have all D3DX DLLs coexist side by side, in order to prevent any backwards compatibility issues. This means that for each new SDK update, the D3DX library has a unique name (d3dx9_24.dll, d3dx9_25.dll, etc.)This of course is a major pain for developers because if the user's runtime doesn't have the correct version, the game won't run. MS tried to find a solution by have a small installer that updates the DLL. Not sure if that works or not.Note: to redistribute the D3DX DLL along with your game WITHOUT the DX runtime is against the EULA.Having said that, if you want the DLL, just look for it on the internet. They are all available for DL.   ;Quote:Original post by voguemasterThey did this as of the Feb 2005 release of the DX SDK. They claim to want to have all D3DX DLLs coexist side by side, in order to prevent any backwards compatibility issues. This means that for each new SDK update, the D3DX library has a unique name (d3dx9_24.dll, d3dx9_25.dll, etc.)So you're telling me that although I have DX9.0c, I don't have the right version of DX9.0c? [rolleyes] Thats just dandy.   ;  Not quite. You have ONE version of the D3DX library. The developer has another and linked his application against it (although it's transparent to him). You need his version in order to run his demo.   ;  When I ran it, it said d3dx9_25.dll not found. So I took a d3dx9_27.dll and renamed it to d3dx9_25.dll. Worked fine [smile]. It was very slow though. ~2 FPS. [sad] I'm on a GeForce 5200 256 mb, Intel P3 660 mHz, 256 mb RAM. I don't blame you for the slowness. It was my crappy hardware. The demo was otherwisw very cool [cool].EDIT: When an app wants a specific d3dx9_##.dll I just take another d3dx9_##.dll and it usually works ok. However sometimes when I replace with an older version it crashes.   ;  Unfortunately, yes, OrangyTang. There is the "release" of the DX9.0c - a new release comes out every 3-4 months or so. Microsoft are aware of the problem they have created and say they will "take care of it sometime".... Somehow I can't see that happening ;-)Now regarding the demo. First of all, nice job! However, my FPS really was down. I have a P4-3000 with 1GB RAM, and a Radeon 9600 XP (or PRO, I keep forgetting) with 128MB, and I was at around 19FPS most of the time.   