Hi,

 

I havent posted on AVSIM in ages, but I came across the DX10 fixer in another thread and wanted to post kudos to Steve for this tool.

 

I want to echo the thanks of the community for this set of fixes and packaging them up in an easy to access tool. This certainly takes the DX10 implementation much further and much closer to what we intended before the schedule got cut on us.

 

So thanks Steve!

 

Phil

 

PS, Its hard to realize that in January we get the 5 year anniversary of Microsofts' decision to close the studio and cancel the game. Got to thank Phil Spencer for that one again.

 

Let me add my thanks directly to a flight sim legend.  I also hope to see you in the forums again.

I would like to extend a thanks to you directly

 

+1

 

FSX is the ONLY 'game' I play nowadays. A lot of games came and went again and I stopped playing games altogether now... apart from the game of games: FSX! Thanks for all those years of joy I had in the past and all the years I still have ahead! ^_^ And of course this goes out to all the team members who worked on this classic sim!!!

 

Back OT: Because of performance differences I still use DX9 right now but things may change when the A2A C172R has been released. My current plane, the Lancair Legacy doesn't have any VC-shadows but that C172R will certainly have them and I did notice (in MS Flight........) how immersive such a 'simple' feature can be. So I will certainly give DX10 a try again when the A2A plane has been released!

They're fixed, Fly, along with dozens of other fixes and additions - like slow snow....  :lol:

 

NICE!  I think I can hold out but not sure lol.  I just tested DX9 again, and I don't know if it's the different drivers I'm running now or what but I'm actually getting decent FPS over Seattle in FTX PNW in DX9 so I might go back until the tool comes out.  That addon was a big reason I was trying to go DX10 because I was getting slightly better fps with it.  I was running some 310.x drivers at the time and after a bad experience with the latest and greatest that was out a couple months ago, I went to 314.22 and things have been great of course but maybe those are helping DX9 mode too.

Just a question for the beta testers if you don't mind....

 

Can any of you confirm if aircraft lights (default and payware) work 100%?

 

I only have one payware aircraft where the lights work perfect in DX10.  With everything else, nav/strobe are only visible from certain angles.  Beacons don't work, but their reflections on the aircraft does. 

 

I really want to go DX10 but these lighting issues are holding me back.  I get smoother performance in DX10 and I love the color saturation.

 

If the lights work perfect on the beta, I'm getting this add on as soon as it comes out.

 

Thanks

 

Mr. Phil Taylor,

Thanks for your input.  We're so thankful for all the things you've done for us.  Hope to see you around.

Hi,

 

I havent posted on AVSIM in ages, but I came across the DX10 fixer in another thread and wanted to post kudos to Steve for this tool.

 

I want to echo the thanks of the community for this set of fixes and packaging them up in an easy to access tool. This certainly takes the DX10 implementation much further and much closer to what we intended before the schedule got cut on us.

 

So thanks Steve!

 

Phil

 

PS, Its hard to realize that in January we get the 5 year anniversary of Microsofts' decision to close the studio and cancel the game. Got to thank Phil Spencer for that one again.

Ha, what a nice and unexpected surprise.

 

I think we all have to thank you and your team for the amazing piece of software so many of us are still enjoying. It's really special that a simulator/game is still so much alive after all these years after being cancelled. Many third party developers are very successful with building upon the solid open platform you guys delivered.

 

It's too bad that there isn't much room left for optimizing performance with today's hardware, because the development of technology went forward in a different direction than could be expected back then. Still, with the efforts of Steve and others we all can enjoy this masterpiece in simulation software better than ever.

 

Cheers! :drinks:

Groovin_DC-10, on 01 Sept 2013 - 10:22 PM, said:

 

Can any of you confirm if aircraft lights (default and payware) work 100%?

 

I only have one payware aircraft where the lights work perfect in DX10. With everything else, nav/strobe are only visible from certain angles. Beacons don't work, but their reflections on the aircraft does.

 

I really want to go DX10 but these lighting issues are holding me back. I get smoother performance in DX10 and I love the color saturation.

 

If the lights work perfect on the beta, I'm getting this add on as soon as it comes out.

Hi Maurice; I'm sorry to hear that it all hinges on the aircraft lights being "perfect", because not all aircraft's lights are "perfect" in DX9, let alone DX10! Not only lighting issues, but memory issues, stuttering issues, framerate issues, and as you noted - graphics quality and smoothness issues, too, and so on.... DX9 is not "perfect" by a long shot.

Those are the major reasons that have kept me in DX10 for over a year!

 

I can tell you this;

 

1). All default aircraft lighting works properly in DX10.

2). Where the developer has used aircraft lighting methods as per the the SDK - all addon aircraft lighting works properly in DX10, as shown below.

 

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit

light.0 = 3, -2.76, -18.11, 2.97, fx_navred

light.1 = 3, -2.78, 18.11, 2.95, fx_navgre

light.2 = 2, -3.13, -18.31, 2.95, fx_strobe

light.3 = 2, -3.11, 18.31, 2.95, fx_strobe

light.4 = 1, -20.51, 0.00, 6.20, fx_beacon

light.5 = 4, -2.27, 0.00, 1.45, fx_vclight

 

3). Where the developer has used aircraft lighting methods which are "custom-made", as below, or maybe included inside the .mdl file - as in the IRIS BD5-J, where the VC lights don't even work in DX9 at night, then the aircraft lighting may - or may not work properly.

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo

light.0=3, -1.7, -25.8, 2.1, fx_esdg_navred

light.1=3, -1.7, 25.8, 2.1, fx_esdg_navgre

light.2=7, -24.4, 0.1, 3.11, fx_navwhi

light.3=10, 11.50, 0.30, 2.60, cit_II_panelflood

light.4=10, 11.50, -0.30, 2.60, cit_II_panelflood

light.5=2, -1.85, -25.8, 2.1, ESDGstrobe

light.6=2, -1.85, 25.8, 2.1, ESDGstrobe

light.7=8, 13.0, -18.5, 8.60, cit_II_icelight //rightwing icelight

light.8=8, 13.0, 18.5, 8.60, cit_II_icelight //leftwing icelight

light.9=9, -23.2, -1.15, 13.15, Cit_II_logo

light.10=9, -23.2, 1.15, 13.15, Cit_II_logo

light.11=5, 6.50, 0.00, 2.60, cit_II_panelflood

light.12=5, 3.50, 0.00, 2.60, cit_II_panelflood

light.13=5, -3.50, 0.00, 2.60, cit_II_panelflood

 

I hope this helps! :wink:

 

All the Best,

 

pj

Since we're jawing about things being addressed in Steve's fixer, I have one I'd like to ask about: Not sure if it's smoke or afterburner effects, but with certain addon aircraft, I sometimes notice that the smoke trails or afterburner/engine flames that should be coming from the engine(s) are actually appearing several hundred yards ahead of the aircraft. Particularly apparent on my MilViz aircraft (but i think I've seen it in a few others as well).

Somewhere in the aircraft.cfg, OB, you will find a line or two, and a heading, like this:-

 

[sMOKESYSTEM]

smoke.0= -49.250, -9.186, 2.296, maddog_smoke
smoke.1= -49.250,  9.186, 2.296, maddog_smoke   ... from the LH Maddog, and this one:-

 

[smokesystem]
smoke.0 = -5.5, 0, -3.0, fx_christeneagle_smoke
smoke.1 = -6.5, 0, -3.0, fx_christeneagle_smoke1........... from the IRIS Christen Eagle.

 

OK! Have fun, play with the numbers until the smoke touches the backend!


 

Since we're jawing about things being addressed in Steve's fixer, I have one I'd like to ask about: Not sure if it's smoke or afterburner effects, but with certain addon aircraft, I sometimes notice that the smoke trails or afterburner/engine flames that should be coming from the engine(s) are actually appearing several hundred yards ahead of the aircraft. Particularly apparent on my MilViz aircraft (but i think I've seen it in a few others as well).

 

I found a weird one the other night.  I can only assume it is DX10 related as I've never seen it before.  Landing at YBRM after just installing FTX's Australia package and was in the Qualitywing Avro RJ100.  It was getting close to dusk (but not there yet, still showed as day in "time/date") so shadows were long.  When  I landed on rwy 10 the aircraft shadow was literally reversed.  It wasn't just that the high T tail kinda showed in front, it was accurately reversed with the straight edges from the trailing edge of the stabilizer and wings on the far side in front of the aircraft.  Should have got a pic of it.  It was showing correctly when I parked on the tarmac (facing the other direction incidentally) so I wonder if it's related to runway fixes in the shaders.  I seem to remember reading something about flashing runways being fixed as part of them.  Maybe FSX just doesn't handle being "upside down" in the Southern Hemisphere very well with shadows lol  :lol:

Somewhere in the aircraft.cfg, OB, you will find a line or two, and a heading, like this:-

 

[sMOKESYSTEM]

 

smoke.0= -49.250, -9.186, 2.296, maddog_smoke

smoke.1= -49.250,  9.186, 2.296, maddog_smoke   ... from the LH Maddog, and this one:-

 

[smokesystem]

smoke.0 = -5.5, 0, -3.0, fx_christeneagle_smoke

smoke.1 = -6.5, 0, -3.0, fx_christeneagle_smoke1........... from the IRIS Christen Eagle.

 

OK! Have fun, play with the numbers until the smoke touches the backend!

 

 

 

 

I think I see what you're getting at with this suggestion Paul, but I fear the problem is more complicated than that. It's DX10 specific (so wouldn't your fix 'break' it in DX9?) and also dependent on if the aircraft is loaded 'fresh' or after another 'working' one, which apparently does some sort of initialization that 'fixes' the problem. It also only appears in certain views (I think)... so simply repositioning the smoke trail I don't think is the answer. However, before I dismiss it, I'll have a more detailed look. Thanks!

Why not just ask over at the Milviz forum? You might get the precise fix, as - maybe - it's an already known issue?.

 

It's not a 'fix' by any means: those numbers are simply the location of the beginning point relative to the aircraft datum line - same as your eye position in the VC, or the position of the landing light.

 

 

Why not just ask over at the Milviz forum? You might get the precise fix, as - maybe - it's an already known issue?.

Milviz does NOT support DX10 and does NOT support Windows 8, so they essentially blow me off whenever I come up with a support issue or question. (On top of being generally rude and snarly to paying customers ). If I didn't love their stuff so much or was unable to find workarounds or simply ignore some of the issues I have, I would have sent the stuff back and moved on.

If it can solve the lack of textures on FS9 planes in FSX, and also eliminate the "double runway" problem that I have at UK2000 Gatwick Xtreme (and any others that I may have missed) in DX10 mode, then consider me interested.

 

 

"double runway" problem that I have at UK2000 Gatwick Xtreme

 

Do you have a picture of this so I can compare, I don't have this problem.

Hi Maurice; I'm sorry to hear that it all hinges on the aircraft lights being "perfect", because not all aircraft's lights are "perfect" in DX9, let alone DX10! Not only lighting issues, but memory issues, stuttering issues, framerate issues, and as you noted - graphics quality and smoothness issues, too, and so on.... DX9 is not "perfect" by a long shot.

Those are the major reasons that have kept me in DX10 for over a year!

 

I can tell you this;

 

1). All default aircraft lighting works properly in DX10.

2). Where the developer has used aircraft lighting methods as per the the SDK - all addon aircraft lighting works properly in DX10, as shown below.

 

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit

light.0 = 3, -2.76, -18.11, 2.97, fx_navred

light.1 = 3, -2.78, 18.11, 2.95, fx_navgre

light.2 = 2, -3.13, -18.31, 2.95, fx_strobe

light.3 = 2, -3.11, 18.31, 2.95, fx_strobe

light.4 = 1, -20.51, 0.00, 6.20, fx_beacon

light.5 = 4, -2.27, 0.00, 1.45, fx_vclight

 

3). Where the developer has used aircraft lighting methods which are "custom-made", as below, or maybe included inside the .mdl file - as in the IRIS BD5-J, where the VC lights don't even work in DX9 at night, then the aircraft lighting may - or may not work properly.

 

[LIGHTS]

//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo

light.0=3, -1.7, -25.8, 2.1, fx_esdg_navred

light.1=3, -1.7, 25.8, 2.1, fx_esdg_navgre

light.2=7, -24.4, 0.1, 3.11, fx_navwhi

light.3=10, 11.50, 0.30, 2.60, cit_II_panelflood

light.4=10, 11.50, -0.30, 2.60, cit_II_panelflood

light.5=2, -1.85, -25.8, 2.1, ESDGstrobe

light.6=2, -1.85, 25.8, 2.1, ESDGstrobe

light.7=8, 13.0, -18.5, 8.60, cit_II_icelight //rightwing icelight

light.8=8, 13.0, 18.5, 8.60, cit_II_icelight //leftwing icelight

light.9=9, -23.2, -1.15, 13.15, Cit_II_logo

light.10=9, -23.2, 1.15, 13.15, Cit_II_logo

light.11=5, 6.50, 0.00, 2.60, cit_II_panelflood

light.12=5, 3.50, 0.00, 2.60, cit_II_panelflood

light.13=5, -3.50, 0.00, 2.60, cit_II_panelflood

 

I hope this helps! :wink:

 

All the Best,

 

pj

 

Thank you very much for your help, Paul.  I think I will get this on release day.  I was just doing some thinking and realized, that it's really no big deal.  I'm sure I can live with it as it is a small price to pay for the extra performance and graphical upgrade.  Still keeping my fingers crossed that the lights will work on all my favorite aircrafts. 

 

Once I get Steve's fixer, would I need anything else as well?  Wondering if I'd have to set AA and VSync manually?

 

At the moment, I don't have any of the DX10 fixes from here activated because I'm currently running a new install (still in DX9) since I just upgraded to SSD.  I plan on going back to DX10 when the fixer is out.  Is the expected release date still this Sept?

 

Thanks again.