Status update... The problem goes away if I uninstall the SteveFX fixer libraries, even in DX10. I am now working with Steve to troubleshoot the culprit. Will report back.

Yes... Doomed!

Further status update and "final" (sort of) resolution....

I have been in touch with Steve and we were able to narrow the problem down to a specular map option on the VC surface which results in a dark alpha channel. By going to the DX10 Controller debug screen and unckecking "Fix Diffuse Specular Bug" the problem goes away and all other options and fixer settings continue to work normally. 

I am calling this a victory and a day.

Doomed no more... 

1 minute ago, pilotmarcog said:

I am calling this a victory and a day.

Why not do something more enjoyable now?  Like flying....  Enjoy.  I will be flying my GNS equipped RA Duke v2 (non-turbine) this week.

On 7/7/2020 at 9:12 AM, pilotmarcog said:

It appears my post on the official thread was deleted.

Hi, no it was not, it was split in its own discussion which you can find easily just in reviewing where are your posts in your "Profile" view!

I'm glad you've sorted this all out!

Edited July 8, 20205 yr by RXP

Just to add detail to this.  

The underlying reason is that the real air duke uses a material property for  a flat  layer drawn on top of the display area of BLENDDIFFUSEBYINVERSESPECULARMAPALPHA  (Snappy huh?). 
This has always been completely broken in both the dx9 and dx10 fsx shaders and nothing using it ever gets drawn as they fail to compile. 

My fixer corrects the bug in the shader and hence everything is drawn correctly based on the supplied texture.  This texture has an adjustment to the alpha channel for the area where the default gps goes and hence you can see it . The Specular  texture lacks this cutout in the area the 650 was placed and hence it was obscured.  In dx9 this didn’t happen because of the broken shader...

I have advised Marco how to disable the fix and rebreak the shader. There is some risk that some other aircraft will now not appear exactly as specified but if so they would have never have appeared correctly without the fixer ( and never appeared correctly in dx9) so it cannot be a big loss.

if anyone else reports this then refer them to me.

 

Edited July 8, 20205 yr by SteveFx

4 hours ago, fppilot said:

Why not do something more enjoyable now?  Like flying....  Enjoy.  I will be flying my GNS equipped RA Duke v2 (non-turbine) this week.

Hmm... I wonder if I should venture to try to get the GTN's in there also... Doomed again?

Edited July 8, 20205 yr by pilotmarcog

1 hour ago, pilotmarcog said:

Hmm... I wonder if I should venture to try to get the GNT's in there also... Doomed again?

Take some time off...  LOL!  I just recently got the GNS's working in the Duke and needed a lot of help getting it done.  Not sure if I can remember all of it.  Duke installer/configuration app.  Had to be tricked as it only handles the legacy RXP GNS, not v2.  Then mods to panel.cfg and the gns related .ini file, and then I believe a couple of extraneous files to copy perhaps into the simulator's (FSX in my case) Gauges folder. I have the panel and .ini file well backed  up.  The other steps I would need to track back and untangle so to speak.

3 minutes ago, fppilot said:

Take some time off...  LOL!  I just recently got the GNS's working in the Duke and needed a lot of help getting it done.  Not sure if I can remember all of it.  Duke installer/configuration app.  Had to be tricked as it only handles the legacy RXP GNS, not v2.  Then mods to panel.cfg and the gns related .ini file, and then I believe a couple of extraneous files to copy perhaps into the simulator's (FSX in my case) Gauges folder. I have the panel and .ini file well backed  up.  The other steps I would need to track back and untangle so to speak.

Don't worry. I will take at least 1 day off :P.... Right now cleaning up the Comanche 250 mod. That seems to be holding up pretty well. Thanks for all the help

On 7/8/2020 at 12:40 PM, pilotmarcog said:

Further status update and "final" (sort of) resolution....

I have been in touch with Steve and we were able to narrow the problem down to a specular map option on the VC surface which results in a dark alpha channel. By going to the DX10 Controller debug screen and unckecking "Fix Diffuse Specular Bug" the problem goes away and all other options and fixer settings continue to work normally. 

I am calling this a victory and a day.

Doomed no more... 

Wow. Now I have the same issue.  Long story short, late last week I lost my system while making a system clone SSD.  Neither my "C:\"  drive or the clone would boot and I could not recover.   So on with a totally fresh W10 start from the ground up.  When it came time for my FSX reinstall (Gold), Acceleration would not activate.  So, on to FSX Steam. I can see the files on the failed SSD so I can access most of the files I need, including scenery and FSUIPC profiles.

But alas. After fresh installs and moving panel.cfg and RXP .ini file, of the pair of GTN's I have been usiing in FSX, the RXP GTN 750_1 works as it should, but in Steam the RXPGTN 750_2 stays dark, both the VC and the pop-up.  I have deleted and reinstalled all three products to no avail.  My second GTN stays dark.  I am not using DX10 or Steve's fixer.  

I have looked back through topics and through my emails and cannot located the instructions I used to first configure the pair of GTN 750's.  Am I missing a step by just copying over my panel.cfg file and RealityXP.GTN.ini files?  I also tried copying over the TDv2's files from the RealAir folder in my FSX files.  The only mods I can find history of were for one F1GTN 750.

Any ideas??/

I managed to make the second GTN gauge brighter by editing this RA Turbine Duke V2 file:

RAS_Gauge_Glass.dds

with Photoshop to make the alpha channel more transparent. One could probably get the same result by renaming the file since that eliminates the glass texture from almost all the gauges. According to MCX, when I load the TD's VC model, the above texture file applies to all the gauges except the GTN 750, which is very odd. It might have something to do with the TD configuration utility.

24 minutes ago, jabloomf1230 said:

I managed to make the second GTN gauge brighter by editing this RA Turbine Duke V2 file:

RAS_Gauge_Glass.dds

with Photoshop to make the alpha channel more transparent. One could probably get the same result by renaming the file since that eliminates the glass texture from almost all the gauges. According to MCX, when I load the TD's VC model, the above texture file applies to all the gauges except the GTN 750, which is very odd. It might have something to do with the TD configuration utility.

That made no difference.

13 hours ago, fppilot said:

That made no difference.

It is both the VC and the popup so do not believe it is an RA panel texture.  Worked fine in FSX.  This is now in Steam Edition.

On 8/4/2020 at 10:29 AM, fppilot said:

It is both the VC and the popup so do not believe it is an RA panel texture.  Worked fine in FSX.  This is now in Steam Edition.

Solved.  Needed to use the eCommerce installers from the RXP website and install through the F1 wrapper.  Everything good to go now.  Back in the air tomorrow, now with FSX-SE and a fresh W10 install.

@fppilot Sorry I didn´t respond sooner. Crazy times we're living! 

Glad to hear it was solved. Even when I was having my problems it would work fine with DX9. My particular situation was directly related to DX10.

Blue skies!

 

Hi guys. I just went through this forum for almost a day, tried everything single thing I could possibly try, and failed every single time to get the GTN750 running in the  RealAirTurbine Duke v2 in FSX:AccPack. I'm extremely frustrated but I can't change the fact, that outside of installing some simple mods everything more complex is beyond my capabilities. So I hope someone can explain to me in a very simple way, how I can get this nice kit from RXP running in my Turbine Duke.

Thank you people in advance.