New Release D3D9Client Development

jarmonik · Nov 3, 2014

eddievhfan1984 said:
I've had an issue myself, running NASSP 7.0 beta: At random times within 6 minutes of simulation startup, regardless of screen mode, communication with the renderer seems to stop, and I get the dialog box telling me to restart the sim.

That is known to happen when Alt-Tabing in a true full-screen mode or pressing Ctrl-Alt-Delete. I have no idea what else in your case could cause that. But it's a good idea the check the D3D9ClientLog if there are any errors. Also, you can press Ctrl+Shift+C to bring up a statistics display. That will show available video memory and surface allocation. If there is a major video memory leak then you should be able to see that. The last option is to run the application with a debugger attached and directX in a debug mode. Whether it gives anything useful is unknown.

Ripley · Nov 3, 2014

I can't find the solution to a problem a user reported some time ago.
Now a user at FOI has the same issue: in his orbiter_ng Launchpad there is no Video tab showing.

Can somebody refresh my memory? How can I help him solve this?

DaveS · Nov 3, 2014

Ripley said:
I can't find the solution to a problem a user reported some time ago.
Now a user at FOI has the same issue: in his orbiter_ng Launchpad there is no Video tab showing.

Can somebody refresh my memory? How can I help him solve this?

By activating one of the external graphics modules such as D3D7 or D3D9.

orb · Nov 3, 2014

If the Video tab is still missing after activating a graphics client module, then there's a missing dependency (e.g. vcredist, DirectX, etc.).

Ripley · Nov 3, 2014

Of course I meant the problem shows after activating D3D9Client module...
Ok, thanks, we'll check the dependencies then.

orb · Nov 3, 2014

If that doesn't help, then there might be also lack of SSE2/3 instructions set in CPU on the target computer.

Anyway, problems with loading the module should be logged in the orbiter.log file with a number of the error (which would help identifying why it didn't load).

Ripley · Nov 4, 2014

orb said:
If that doesn't help, then there might be also lack of SSE2/3 instructions set in CPU on the target computer...

Turned out to be the case, the CPU being an AMD Athlon XP (SSE).
Time to upgrade :tiphat:

This is the error in log

Code:

Error loading module Modules\Plugin\D3D9Client.dll (code -1073741795)

Full story:
http://orbiteritalia.forumotion.com/t2828-problemi-installazione-d3d9

n122vu · Nov 5, 2014

I just did a fresh install of Orbiter 2010 P1, Orbiter Sound, and then D3D9Client R14. I'm getting the "DirectX runtimes may be missing" error when trying to launch a scenario.

Verified the February 2010 runtimes are installed and the necessary DLLs are in the C:\Windows\System32 folder. Is there something else I may have missed?

Orbiter.log:

Code:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.53902e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 140930, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]

**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Surface.cpp Line:1779 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
D3D9TextMgr.cpp Line:581 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
D3D9Pad.cpp Line:107 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
D3D9Client: [Compiling Effects for Shader Model 3.0]
D3D9Effect.cpp Line:260 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, macro, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/D3D9Client.fx)
Scene.cpp Line:1755 Error:-2147024770 D3DXCreateEffectFromFile(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/SceneTech.fx)

D3D9Client.log:

Code:

(0: 0.00s 24288747991us)(0x2550) ================ clbkInitialise ===============
(1: 0.00s 24288748044us)(0x2550) Orbiter Version = 100830
(2: 0.02s 24288769633us)(0x2550) Index:0 640 x 480 60Hz (22)
(3: 0.02s 24288769920us)(0x2550) Index:1 640 x 480 72Hz (22)
(4: 0.02s 24288770282us)(0x2550) Index:2 640 x 480 75Hz (22)
(5: 0.02s 24288770617us)(0x2550) Index:3 768 x 480 56Hz (22)
(6: 0.02s 24288770954us)(0x2550) Index:4 768 x 480 60Hz (22)
(7: 0.02s 24288771287us)(0x2550) Index:5 768 x 480 72Hz (22)
(8: 0.03s 24288771616us)(0x2550) Index:6 768 x 480 75Hz (22)
(9: 0.03s 24288771949us)(0x2550) Index:7 800 x 600 56Hz (22)
(10: 0.03s 24288772272us)(0x2550) Index:8 800 x 600 60Hz (22)
(11: 0.03s 24288772605us)(0x2550) Index:9 800 x 600 72Hz (22)
(12: 0.03s 24288772935us)(0x2550) Index:10 800 x 600 75Hz (22)
(13: 0.03s 24288773267us)(0x2550) Index:11 848 x 480 60Hz (22)
(14: 0.03s 24288773583us)(0x2550) Index:12 848 x 480 70Hz (22)
(15: 0.03s 24288773900us)(0x2550) Index:13 848 x 480 75Hz (22)
(16: 0.03s 24288774221us)(0x2550) Index:14 960 x 600 60Hz (22)
(17: 0.03s 24288774544us)(0x2550) Index:15 960 x 600 70Hz (22)
(18: 0.03s 24288774874us)(0x2550) Index:16 960 x 600 75Hz (22)
(19: 0.03s 24288775198us)(0x2550) Index:17 1024 x 600 60Hz (22)
(20: 0.03s 24288775533us)(0x2550) Index:18 1024 x 600 70Hz (22)
(21: 0.03s 24288775871us)(0x2550) Index:19 1024 x 600 75Hz (22)
(22: 0.03s 24288776181us)(0x2550) Index:20 1024 x 768 60Hz (22)
(23: 0.03s 24288776516us)(0x2550) Index:21 1024 x 768 70Hz (22)
(24: 0.03s 24288776848us)(0x2550) Index:22 1024 x 768 75Hz (22)
(25: 0.03s 24288777176us)(0x2550) Index:23 1280 x 720 60Hz (22)
(26: 0.03s 24288777497us)(0x2550) Index:24 1280 x 768 60Hz (22)
(27: 0.03s 24288777830us)(0x2550) Index:25 1280 x 800 60Hz (22)
(28: 0.03s 24288778163us)(0x2550) Index:26 1280 x 1024 60Hz (22)
(29: 0.03s 24288778482us)(0x2550) Index:27 1280 x 1024 75Hz (22)
(30: 0.03s 24288778815us)(0x2550) Index:28 1360 x 768 60Hz (22)
(31: 0.03s 24288779156us)(0x2550) Index:29 1366 x 768 60Hz (22)
(32: 0.03s 24288779487us)(0x2550) Index:30 1440 x 900 60Hz (22)
(33: 0.03s 24288779626us)(0x2550) Index:31 1600 x 1200 60Hz (22)
(34: 0.03s 24288779717us)(0x2550) Index:32 1680 x 1050 59Hz (22)
(35: 0.03s 24288779751us)(0x2550) Index:33 1680 x 1050 60Hz (22)
(36: 0.03s 24288779780us)(0x2550) Index:34 1920 x 1080 60Hz (22)
(37: 0.03s 24288779822us)(0x2550) Index:35 1600 x 900 60Hz (22)
(38: 0.03s 24288779859us)(0x2550) Index:36 1400 x 1050 60Hz (22)
(39: 0.03s 24288779889us)(0x2550) Index:37 1280 x 960 60Hz (22)
(40: 18.21s 24306955527us)(0x2550) Node[1] = 2010 Edition (0x250738)
(41: 18.21s 24306955564us)(0x2550) Node[0] = Welcome (0x279F40)
(42: 18.21s 24306955576us)(0x2550) Scenario = .\Scenarios\2010 Edition\Welcome.scn
(43: 18.21s 24306957863us)(0x2550) ================ clbkCreateRenderWindow ===============
(44: 18.23s 24306974878us)(0x2550) [VideoConfiguration] Adapter=0, ModeIndex=0
(45: 18.23s 24306975143us)(0x2550) Adapter = NVIDIA NVS 5400M 
(46: 18.23s 24306975161us)(0x2550) dwFSMode = 0
(47: 18.23s 24306975180us)(0x2550) MaxTextureBlendStages..: 8
(48: 18.23s 24306975191us)(0x2550) MaxTextureWidth........: 16384
(49: 18.23s 24306975201us)(0x2550) MaxTextureHeight.......: 16384
(50: 18.23s 24306975210us)(0x2550) MaxPrimitiveCount......: 16777215
(51: 18.23s 24306975220us)(0x2550) MaxVertexIndex.........: 16777215
(52: 18.23s 24306975230us)(0x2550) MaxAnisotropy..........: 16
(53: 18.23s 24306975239us)(0x2550) MaxSimultaneousTextures: 8
(54: 18.23s 24306975249us)(0x2550) MaxStreams.............: 16
(55: 18.23s 24306975258us)(0x2550) MaxStreamStride........: 255
(56: 18.23s 24306975268us)(0x2550) MaxVertexBlendMatrices.: 4
(57: 18.23s 24306975277us)(0x2550) MaxVShaderInstrExecuted: 65535
(58: 18.23s 24306975286us)(0x2550) MaxPointSize...........: 8192.000000
(59: 18.23s 24306975297us)(0x2550) VertexShaderVersion....: 0x300
(60: 18.23s 24306975306us)(0x2550) PixelShaderVersion.....: 0x300
(61: 18.23s 24306975315us)(0x2550) NumSimultaneousRTs.....: 4
(62: 18.23s 24306975325us)(0x2550) D3DPTEXTURECAPS_POW2...: 0
(63: 18.23s 24306975334us)(0x2550) NONPOW2CONDITIONAL.....: 0
(64: 18.23s 24306975343us)(0x2550) VertexDeclCaps.........: 0x30F
(65: 18.23s 24306975352us)(0x2550) DevCaps................: 0x1BBEF0
(66: 18.23s 24306975362us)(0x2550) DevCaps2...............: 0x51
(67: 18.23s 24306975371us)(0x2550) XNA Math Support.......: Yes
(68: 18.23s 24306975694us)(0x2550) D3DFMT_D32F_LOCKABLE
(69: 18.23s 24306975720us)(0x2550) D3DFMT_D24S8
(70: 18.23s 24306975738us)(0x2550) D3DFMT_D24X8
(71: 18.23s 24306975753us)(0x2550) Window Size = [1018, 550]
(72: 18.25s 24307001537us)(0x2550) Available Texture Memory = 4037 MB
(73: 18.26s 24307004240us)(0x2550) ----- Initialize D3D9ClientSurface Tech -----
(74: 18.26s 24307005356us)(0x2550)[ERROR] D3D9Surface.cpp Line:1779 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
(75: 18.26s 24307005641us)(0x2550)[ERROR] Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
(76: 19.73s 24308477129us)(0x2550) Render Target = 0x4457B20
(77: 19.73s 24308478334us)(0x2550)[ERROR] D3D9TextMgr.cpp Line:581 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
(78: 19.73s 24308478751us)(0x2550)[ERROR] Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
(79: 20.23s 24308972418us)(0x2550)[ERROR] D3D9Pad.cpp Line:107 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
(80: 20.23s 24308972813us)(0x2550)[ERROR] Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
(81: 20.67s 24309416620us)(0x2550) [NEW FONT] ( Courier New), Size=20, Weight=400 Pitch&Family=31
(82: 20.67s 24309421272us)(0x2550) Font Video Memory Usage = 256 kb
(83: 20.68s 24309421820us)(0x2550) Font and Charter set creation succesfull
(84: 20.74s 24309483437us)(0x2550) Starting to initialize basic a rendering technique...
(85: 20.74s 24309483476us)(0x2550) [Compiling Effects for Shader Model 3.0]
(86: 20.74s 24309484946us)(0x2550)[ERROR] D3D9Effect.cpp Line:260 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, macro, 0, 0, 0, &FX, &errors)
(87: 20.74s 24309485223us)(0x2550)[ERROR] Failed to create an Effect (Modules/D3D9Client/D3D9Client.fx)
(88: 20.87s 24309617767us)(0x2550)[ERROR] Scene.cpp Line:1755 Error:-2147024770 D3DXCreateEffectFromFile(pDev, name, 0, 0, 0, 0, &FX, &errors)
(89: 20.87s 24309618158us)(0x2550)[ERROR] Failed to create an Effect (Modules/D3D9Client/SceneTech.fx)

Cras · Nov 6, 2014

Saw there is now an R14 of the D3D9 client. Been using R12, but upgraded because why not. Is there anything different to this release of the client?

Running it in 2010p1 btw, I noticed there is a new beta out there but not touching that yet.

Mojave · Nov 7, 2014

Cras said:
Saw there is now an R14 of the D3D9 client. Been using R12, but upgraded because why not. Is there anything different to this release of the client?

Running it in 2010p1 btw, I noticed there is a new beta out there but not touching that yet.

Additionally, does the beta work in Orbiter 2010p1 because that atmosphere rendering is beautiful and I'd like to be able to use it in my stable installation if that is possible?

jarmonik · Nov 7, 2014

n122vu said:
I just did a fresh install of Orbiter 2010 P1, Orbiter Sound, and then D3D9Client R14. I'm getting the "DirectX runtimes may be missing" error when trying to launch a scenario.

Verified the February 2010 runtimes are installed and the necessary DLLs are in the C:\Windows\System32 folder. Is there something else I may have missed?

I checked the D3D9Client.dll and it seems to require D3DX9_43.dll instead of an intended D3DX9_42.dll So, it would seem that it's build for a newer version of the redistributables. Downloading the latest one would most likely fix the problem.

---------- Post added at 13:37 ---------- Previous post was at 13:31 ----------

Cras said:
Is there anything different to this release of the client?

I don't recall very well. Most likely just a bug fixes. After a summer, I started working on an amateur (HAM) radio receiver and it's been keeping my mind elsewhere for a while. I hope to find some time to implement a few new ideas for this project as well.

---------- Post added at 13:49 ---------- Previous post was at 13:37 ----------

Samuel Edwards said:
Additionally, does the beta work in Orbiter 2010p1 because that atmosphere rendering is beautiful and I'd like to be able to use it in my stable installation if that is possible?

I suppose it might be too early to say anything about it. But I don't think that it's going to be ported to P1. So, the answer is no, at-least for now. There are more important things requiring our attention in the clients.

DaveS · Nov 7, 2014

jarmonik said:
I checked the D3D9Client.dll and it seems to require D3DX9_43.dll instead of an intended D3DX9_42.dll So, it would seem that it's build for a newer version of the redistributables. Downloading the latest one would most likely fix the problem.

---------- Post added at 13:37 ---------- Previous post was at 13:31 ----------

I don't recall very well. Most likely just a bug fixes. After a summer, I started working on an amateur (HAM) radio receiver and it's been keeping my mind elsewhere for a while. I hope to find some time to implement a few new ideas for this project as well.

I'd like to at least see a return of the original specular map behavior and the inclusion of Felix24's R12A changes as well as AO. That would make D3D9Client pretty much complete in my mind.

In the long-term future a change to the way exhausts are rendered to match this description could be implemented.

jarmonik · Nov 7, 2014

DaveS said:
I'd like to at least see a return of the original specular map behavior

I thought I fixed that a long ago. If I recall correctly the problem was that specular map color was modulated with specular material color. And it was returned to it's original behavior where specular map overrides the specular material setting. That fix should be present in R14.

DaveS said:
... and the inclusion of Felix24's R12A changes as well as AO.

I would be happy to include them but I can't just take them without permission. So, if Felix24 could officially post the code changes, then that would help a lot.

DaveS · Nov 7, 2014

jarmonik said:
I thought I fixed that a long ago. If I recall correctly the problem was that specular map color was modulated with specular material color. And it was returned to it's original behavior where specular map overrides the specular material setting. That fix should be present in R14.

I'm talking about this discussion a while back: http://www.orbiter-forum.com/showthread.php?p=473769

jarmonik · Nov 7, 2014

DaveS said:
I'm talking about this discussion a while back: http://www.orbiter-forum.com/showthread.php?p=473769

Yes, the specular behavior of R14 should be equal to R10. Are you saying that it is not ?

Could you check that the *.fx files located in /Modules/D3D9Client/ are actually from R14 distribution package ?

DaveS · Nov 7, 2014

jarmonik said:
Could you check that the *.fx files located in /Modules/D3D9Client/ are actually from R14 distribution package ?

Seems like they didn't extract when I installed it.

n122vu · Nov 7, 2014

jarmonik said:
I checked the D3D9Client.dll and it seems to require D3DX9_43.dll instead of an intended D3DX9_42.dll So, it would seem that it's build for a newer version of the redistributables. Downloading the latest one would most likely fix the problem.

Thanks, this fixed the issue.

For reference, I downloaded the DirectX End-User Runtimes (June 2010) package.

Cras · Nov 7, 2014

Thanks for keeping up with this project, it really helps bring Orbiter to life. You work is always appreciated. Cheers!

Mojave · Nov 7, 2014

jarmonik said:
I suppose it might be too early to say anything about it. But I don't think that it's going to be ported to P1. So, the answer is no, at-least for now. There are more important things requiring our attention in the clients.

Alrighty, I'll just have to keep my fingers crossed on this one.

Really love the work you have done on it so far! long live the d3d9 client.

:cheers:

Donamy · Nov 24, 2014

n122vu said:
Thanks, this fixed the issue.

For reference, I downloaded the DirectX End-User Runtimes (June 2010) package.

I downloaded them also, where do I place the extracted files ?

New Release D3D9Client Development

Well-known member

Tutorial translator

Addon Developer

New member

Tutorial translator

New member

Tutorial translator

Addon Developer

Spring of Life!

60% Ethanol

Well-known member

Addon Developer

Well-known member

Addon Developer

Well-known member

Addon Developer

Addon Developer

Spring of Life!

60% Ethanol

Addon Developer

Similar threads