Thanks for the suggestion. The default settings were very washed out. By changing those settings, I got it much closer to reality. Also I now got the sun to look yellower from Earth
It wouldn't hurt to have the change history copied into a new location but I am OK just having the head revision to start with, which can be downloaded from codeplex.
which version orbiter beta,or orbiter 2010?I wanted to write down that smoke during lift off is still visible below ground level in d3d9 client...
D3D9Client Initialization Failed
DirectX Runtimes may be missing. See /Doc/D3D9Client.doc for more information
**** Orbiter.log
000000.000: Build Oct 31 2015 [v.151031]
000000.000: Timer precision: 3.94757e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000: Module D3D9Client.dll ........ [Build 151030, API 151028]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9Client: [DirectX 9 Initialized]
000000.000: D3D9Client: Sytem has XNA math support
000000.000: D3D9Client: [3DDevice Initialized]
000000.000: D3D9Surface.cpp Line:2274 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
000000.000: D3D9TextMgr.cpp Line:581 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
000000.000: D3D9Pad.cpp Line:107 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
000000.000: D3D9Effect.cpp Line:251 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, macro, 0, 0, 0, &FX, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/D3D9Client.fx)
000000.000: D3D9Client: [Compiling Effects for Shader Model 3.0]
000000.000: PlanetRenderer.cpp Line:137 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, macro, 0, 0, 0, &pShader, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/Surface.fx)
000000.000: Scene.cpp Line:2016 Error:-2147024770 D3DXCreateEffectFromFile(pDev, name, 0, 0, 0, 0, &FX, &errors)
000000.000: Failed to create an Effect (Modules/D3D9Client/SceneTech.fx)
Hi, I am not sure what exactly your setup is so my 'tips' might be wrong.While launching a scenario with OrbiterBeta (v.151104) with D3D9Client for Orbiter Beta r38 found here (http://orbiter-forum.com/showthread.php?p=518714&postcount=3210), I get an error saying
[...]
I have gotten this the last few weeks with several versions of Orbiter and D3D9Client (but this is a new computer, so I have never gotten it to work).
But D3D9Client works on Orbiter2010. Any tips?
[...]
I'm using Windows 10, vanilla Orbiter install, only with required texture packs. Orbiter.exe with inline client works.
Hi, I am not sure what exactly your setup is so my 'tips' might be wrong.
First: Do you *always* get the error on your new machine? Or only on some installations. If only some installations fail, this might be due to Win10 behavior I can't reproduce (I am working on Win7 and have no experience with Win10).
Second: Did you install the runtime libraries? The message "DirectX Runtimes may be missing" assumes that you did not.
The download location for the runtime libraries are in the D3D9Client documentation (as stated by the error message).
Sorry if I can't provide any better help.
/Kuddel
Ah! This might be the clue.Yes, the D3D9Client for Beta always gives me this error when loading up a scenario. But the D3D9Client works for Orbiter2010, and both Orbiter2010 and OrbiterBeta work with inline graphics.
Ah! This might be the clue.
Note that there are two different releases for D3D9Client:
one for Orbiter BETA (named like D3D9ClientBeta12-forBETA r##(r#####).zip )
and one for Orbiter 2010-P1 (named like D3D9ClientR15-for2010-P1(r#####).zip )!
You cannot mix these. Be sure you download and install the correct release for the installation.
/Kuddel
Latest beta build requires d3dx9_43.dll instead of d3dx9_42.dll. So the required DX run-times are newer/later than February 2010. Very likely June 2010 if I remember correctly.
switch (uMsg) {
case WM_INITDIALOG:
{
InitDialog(hWnd,uMsg,wParam,lParam);
SetDlgItemText(hWnd,IDC_FILENAME,CompleteFileIniName);
SendDlgItemMessage(hWnd,IDC_FILENAME,EM_SETREADONLY,TRUE,0);
hChild[CD_VIEW]= CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_VIEWTXT),hDlg,DlgProcViewTxt,LPARAM(this));
hChild[CD_FAIRING]= CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_FAIRING),hDlg,DlgProcFairing,LPARAM(this));
hChild[CD_PLD]= CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_PAYLOADS),hDlg,DlgProcPld,LPARAM(this));
hChild[CD_PARTICLE] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_PARTICLE),hDlg,DlgProcParticle,LPARAM(this));
hChild[CD_MISC] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_MISC),hDlg,DlgProcMisc,LPARAM(this));
hChild[CD_TEX] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_TEX),hDlg,DlgProcTex,LPARAM(this));
hChild[CD_BOOSTER] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_BOOSTERS),hDlg,DlgProcBooster,LPARAM(this));
hChild[CD_CURVE] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_BOOSTER_CURVE),hDlg,DlgProcCurve,LPARAM(this));
[B][COLOR="Red"]hChild[CD_STAGE] = CreateDialogParam(hInst,MAKEINTRESOURCE(IDD_STAGES),hDlg,DlgProcStage,LPARAM(this));[/COLOR][/B]
ShowWindow(GetDlgItem(hWnd,IDC_SAVEINI),SW_HIDE);
return FALSE;
}
BOOL DevModeDlg::StageProc(HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
return oapiDefDialogProc (hWnd, uMsg, wParam, lParam);
}
Latest beta build requires d3dx9_43.dll instead of d3dx9_42.dll. So the required DX run-times are newer/later than February 2010. Very likely June 2010 if I remember correctly.
The D3D9Client doesn't do anything with any CreateDialogParam() calls. It's just the win32 library (User32.lib/dll) function you are using.Hi there,
is there any limit to dialogs with D3D9? I'm having a CTD while defining the 9th dialog as dialogParam, while this is not happening with inline client.
Since the procedure is exactly the same of the previous eight I wonder if the problem is within d3d9 client.
This is strange, but there is nothing in the D3D9Client that should interfere with the CreateDialogParam() calls. But as every DLL used memory different, the behavior is unpredictable when e.g. the Array is not big enough.I used the very same procedure for other 8 dialogs and this is working with inline, so I cannot figure out what disturbes d3d9 :shrug:
EDIT: I'm using orbiter BETA
Sometimes the most obvious things are hardest to see*
[*] personal experience
That's an absolute truth. Sometimes I start to write questions here in the forum and I find what the error is while writing. So if I get to the end of the message without finding the mistake I press submit, otherwise I press cancel :lol:
There is also a conflict between a GDI based dialog (i.e. pop-up) windows and
anti-aliasing in a true fullscreen mode which will disable the anti-aliasing.
It would be necessary to run the program under a debugger and see where the CTD occur and what's stored in a call stack. It would help to diagnose the problem if I could reproduce the CTD on my computer.
Also, does it work if the parent window is set to desktop (i.e. NULL) instead of the render window ?
hChild[CD_STAGE] = CreateDialogParam(hInst, MAKEINTRESOURCE(IDD_STAGES), NULL, DlgProcStage, LPARAM(this));