New Release D3D9Client Development

[N_Molson]

asymmitric runways...

An interesting concept, for sure :hmm:

:lol:

 

[Phoenix]

I suppose the easiest solution would be adding an optional parameter in the runway lights that would make it a single-ended. In that case you would need two runway lights sections, one for each direction. Would this work ?

[FONT=&quot]RUNWAYLIGHTS[/FONT]
[FONT=&quot]SINGLEENDED[/FONT]
[FONT=&quot]END1 -8220 -3 -600[/FONT]
[FONT=&quot]END2 -12670 -12 -3155[/FONT]
[FONT=&quot]WIDTH 100[/FONT]
[FONT=&quot]PAPI 5.0 3.0 257 3 [/FONT]
[FONT=&quot]PAPI 20.0 3.0 -2000 0 [/FONT]
[FONT=&quot]VASI 1.5 152 671[/FONT]
[FONT=&quot]TD_DISP 257[/FONT]
[FONT=&quot]TD_LENGTH 600 [/FONT]
[FONT=&quot]DECISION_DIST 257[/FONT]
[FONT=&quot]APPROACH_START 900[/FONT]
[FONT=&quot]END[/FONT]


[FONT=&quot]RUNWAYLIGHTS[/FONT]
[FONT=&quot]SINGLEENDED [/FONT]
[FONT=&quot]END2 -8220 -3 -600 // Note: END1 and END2 are swapped[/FONT]
[FONT=&quot]END1 -12670 -12 -3155[/FONT]
[FONT=&quot]WIDTH 100[/FONT]
[FONT=&quot]PAPI 5.0 3.0 257 3 [/FONT]
[FONT=&quot]PAPI 20.0 3.0 -2000 0 [/FONT]
[FONT=&quot]VASI 1.5 152 671[/FONT]
[FONT=&quot]TD_DISP 257[/FONT]
[FONT=&quot]TD_LENGTH 600 [/FONT]
[FONT=&quot]DECISION_DIST 257[/FONT]
[FONT=&quot]APPROACH_START 900[/FONT]
[FONT=&quot]END[/FONT]

Asmi has proposed a two parameter solution. I think that might be the way to do it, and for PAPI lighting too. Whatever you think works best, and is easiest to implement.

There are a lot of aerodrome charts at this website, which show runway and PAPI lighting: http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=6&Itemid=13.html

Thanks.

 

[sitha241]

I have a problem

 

[Ripley]

Forgot the attachment?
I don't see PDFs...

 

[sitha241]

Forgot the attachment?
I don't see PDFs...

is that meant for me?
I attached picture..

 

[jarmonik]

I have a problem

View attachment 10826

I have never seen anything like that. Could be a hardware or installation problem. How common is that ? Could you give some graphics hardware specs ? Does it occur in a clean installation of the Orbiter ?

 

[Ripley]

is that meant for me?
I attached picture..

No, it was in response to Phoenix's post who said there was a pdf in his post, but there wasn't any...

 

[Phoenix]

No, it was in response to Phoenix's post who said there was a pdf in his post, but there wasn't any...

Sorry, it did originally. I must have changed my post after you read it.

 

[sitha241]

I have never seen anything like that. Could be a hardware or installation problem. How common is that ? Could you give some graphics hardware specs ? Does it occur in a clean installation of the Orbiter ?

In clean installation no..I have radeon HD 4300/4500 I think..

 

[kuddel]

Hi jarmonik,

I've found an ugly "bug" in my current OapiExtension class:
Orbiter (v111105) seems to (re-)use some of the IDCs - in both 'Visual helpers' dialog as in 'Orbiter: Configure menu bars' dialog[1].
This causes Orbiter to CTD by stack overflow
Note: This only applies to Orbiter v111105 (Beta). Orbiter v100830[2] doesn't have this 'meu bar'.

Attached you'll find the files needed for the patch.

Regards,
Kuddel


[1] the one that you get when you right-click on the menu bar on top. Where you can configure that bars behavior.
[2] The "releases" of jarminik are buil dagainst Orbiter v100830!

P.S.:If someone needs to access the 'Orbiter: Configure menu bars' dialog until this patch is "released", one can disable all of the visual helper hookings by setting the 'DisableVisualHelperReadout' parameter in 'D3D9Client.cfg' to '1'. Beware to set it back to '0' after you're done with configuring the menu bar! When this setting is '1', the visual helpers (axis, forces,...) are not available in D3D9Client! Although, if you are able to compile the Client for 111105, you should be able to re-compile it with the included patch, anyway

 

[Kyle]

Okay, I'm having a pretty annoying issue with this. I've had D3D9 work before, but I've recently had a system restore on my computer to clean things up. Anyways, I've installed d3dx9.ddl, I have Feb 2010 addition of DirectX as instructed, and every time I load now, it's absolutely refusing to work. As soon as it starts, it says the DirectX runtimes are missing. I'm completely at a loss here as to what to do.

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.77528e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module LolaMFD.dll ........... [Build 101108, API 100830]
Module LTV-MFD.dll ........... [Build ******, API 060425]
Module D3D9Client.dll ........ [Build 120928, API 100830]

**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
.\D3D9Surface.cpp Line:1691 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
.\D3D9TextMgr.cpp Line:566 Error:-2147024770 D3DXCreateEffectFromFileA(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/CKBlit.fx)
.\D3D9Pad.cpp Line:95 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:218 Error:-2147024770 D3DXCreateEffectFromFile(pDev, name, macro, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/D3D9Client.fx)
.\Scene.cpp Line:1446 Error:-2147024770 D3DXCreateEffectFromFile(pDev, name, 0, 0, 0, 0, &FX, &errors)
Failed to create an Effect (Modules/D3D9Client/SceneTech.fx)

 

[jarmonik]

Could you check that you have D3DCompiler_42.dll and D3DX9_42.dll in your Windows/System32/ folder. If not then you have an installation problem with your DirectX runtimes.

---------- Post added at 17:03 ---------- Previous post was at 17:02 ----------

Hi jarmonik,

I've found an ugly "bug" in my current OapiExtension class:
Orbiter (v111105) seems to (re-)use some of the IDCs - in both 'Visual helpers' dialog as in 'Orbiter: Configure menu bars' dialog[1].
This causes Orbiter to CTD by stack overflow
Note: This only applies to Orbiter v111105 (Beta). Orbiter v100830[2] doesn't have this 'meu bar'.

Thanks, I'll include this in the next release.

 

[Kyle]

Okay, I got it working. The problem was with D3DCompiler_32.dll, I didn't have it downloaded. Works perfectly now.

 

[Interceptor]

Hello Jarmonik,I have recently installed your D3d9R5 client on my old winXP set up,and the junction points,and symbolic links function does not work,could it be because I never,and never will install service pack3?,I keep getting the message pop up,need vista or win 7 to create symbolic links.thanks

 

[Ripley]

You can still manually copy config and sound folders.

 

[sitha241]

I solved mine problem with textures..

 

[orb]

Hello Jarmonik,I have recently installed your D3d9R5 client on my old winXP set up,and the junction points,and symbolic links function does not work

Do you have it installed on an NTFS or FAT file system? Junctions require Windows 2000 and NTFS, so I don't think it's because you don't have SP3 on your Windows XP, but rather it could be because of incompatible file system.

 

[rstr]

Stereoscopic View

How to enable this stereo view? I just can't figure it out :< I have GeForce GTS450, so it's supported.

Good acheivement !
But I can't get the Stereoscopic 3D mode. What should I do to get it ?

I have a question . how do I make the stereoscopic 3d work. I have purchased nvidia 3d glasses and ir emitter. I have turned on 3d settings in the video settings on high. I don't see any difference in
orbiter from normal viewing to 3d viewing

Czesc, Poscik.
Salut, SolarLiner.
Howdy, RacerX.
See some pre-requisites on what's needed for Orbiter stereoscopic viewing at http://orbiter-forum.com/showthread.php?p=252432&postcount=6 . If there would be any need for posting additional configuration details, just let me know.
Sorry for late response - I wasn't present in the forum for quite some time, and my D3D9 client experience dates back to an old RC10; but I'm pretty sure, jarmonik's and others splendid work will do fine as well with the newest release (kudos !!); I'll do some more 3D testing in widescreen 3-monitor / SLI configuration soon.

Have Fun - Rob

 

[Cosmic Penguin]

Hi! I have this mysterious light blob issue while using almost every night time scenario with a runway in sight with various add-ons using the D3D9 client. Does anybody here have this similar problem? :shrug:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.10518e-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 EnergyConfigurator.dll  [Build ******, API 060425]
Module ProjectOutpostsConfig.dll  [Build 120604, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module AeroBrakeMFD.dll ...... [Build ******, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module AutoFCS.dll ........... [Build ******, API 050206]
Module AutoFCS-STS.dll ....... [Build ******, API 050206]
Module BaseSyncMFD.dll ....... [Build 100616, API 100603]
Module CSSC_Spawner.dll ...... [Build 120331, API 100830]
Module GPCMFD.dll ............ [Build 111222, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
Module uap.dll ............... [Build 110613, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module Meshdebug.dll ......... [Build 100830, API 100830]
Module BurnTimeCalculator.dll  [Build 110301, API 100830]
Module ScnEditorTLE.dll ...... [Build ******, API 060425]
Module ScreenCapture.dll ..... [Build ******, API 060425]
Module D3D9Client.dll ........ [Build 120928, API 100830]

**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Client: [Compiling Effects for Shader Model 3.0]
D3D9Client: [Loading Stars]
D3D9Client: [Loading Constellations]
D3D9Client: [D3D9Client Initialized]
Failed to get Stereo State
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
BaseObject: Parse error
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module multistage2.dll ....... [Build ******, API 050206]
Module slc17b.dll ............ [Build 100923, API 100830]
Module slc17a.dll ............ [Build 100923, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
D3D9Client: [Scene Initialized]
Module Train.dll ............. [Build 120629, API 100830]
Module XR5Crane.dll .......... [Build 120519, API 100830]
Module ThemLPad.dll .......... [Build 120519, API 100830]
Module RadarDish.dll ......... [Build 120519, API 100830]
Module BigPad.dll ............ [Build 120519, API 100830]
---------------------------------------------------------------
>>> WARNING: CWD modified by module OrbiterSound - Fixing.
---------------------------------------------------------------
Finished setting up render state
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiGetStationCount
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------

 

[blixel]

Hi! I have this mysterious light blob issue while using almost every night time scenario with a runway in sight with various add-ons using the D3D9 client. Does anybody here have this similar problem? :shrug:

Yes. I've seen this same thing several times, but I've never been able to figure out how to reliably recreate the problem. I only see the visual blob when I have the external view open, and it only happens from certain angles. It's never caused any actual problems, so I've just ignored it, but it would be nice if the problem could be located and solved.