Well.. I did further testing and real light and true glass is a no go for the qw 787

keeps getting the same error.

thanks

mike

Weird it's taking them so long to stabilize these add-ons

1 minute ago, Shomron said:

Weird it's taking them so long to stabilize these add-ons

Who knows!

Hoping it is fixed soon.

mike

11 hours ago, micstatic said:

It doesn't matter which plane.  Anyone like the MD80 which uses it.  FYI, I'm not turning it off on an aircraft level.  I'm just going into the V5/gauges directory and renaming trueglass.dll to trueglass.off.  

Sticky for now 😉

It saved my  sceduled Maddog- X flight yesterday

Michael Moe

Yeah, basically what I already tried to tell and explain on page 1 🙂 So while we are on page 4 now, I try it again..

4 hours ago, Shomron said:

Weird it's taking them so long to stabilize these add-ons

It's not that weird because TFDi makes heavy usage of SDK / PDK functions which seem to have changed in the process from going to DX11 to DX12.
Since then, TFDi is constantly trying to nail the issues down. Their recent update is only days old, they completely rewrote RealLight and TrueGlass into DX12 from DX11 which reduced VRAM usage, but it seems it still didn't fix stability.

717 users may remember v4, where they had this annoying "view-switch-CTD-bug" which took them years to resolve it. Now, the 717 works like a charm in v4, very stable and smooth. But in v5, it seems like it will take some time again to get to this point and this goes for TrueGlass and RealLight as well.

But: TFDi does have an official Discord server where you can assign yourself a "testers role" and get access to testers channels, if you like. There, they openly communicate with everybody so I think it would help if people with issues go in there and tell them exactly what happened when the crash occurs / give them some logs if possible. They also release fresh builds of the .dlls (RL and TG) from time to time directly on this discord and ask for feedback.

Like I said, they completely recoded both components just days ago, so there will be still issues in it but if everybody helps them, they may be able to resolve this issue faster.
At the same time, it may be neccessary to wait for v5.1 and Lockheed Martin again. It's most likely a small but very annoying and not easy to find bug to nail down..

Discord: https://tfdidesign.com/chat

Edited September 4, 20205 yr by roesti

Yes I’m part of the group and currently working with them on this issue 

3 hours ago, roesti said:

Yeah, basically what I already tried to tell and explain on page 1 🙂 So while we are on page 4 now, I try it again..

It's not that weird because TFDi makes heavy usage of SDK / PDK functions which seem to have changed in the process from going to DX11 to DX12.
Since then, TFDi is constantly trying to nail the issues down. Their recent update is only days old, they completely rewrote RealLight and TrueGlass into DX12 from DX11 which reduced VRAM usage, but it seems it still didn't fix stability.

717 users may remember v4, where they had this annoying "view-switch-CTD-bug" which took them years to resolve it. Now, the 717 works like a charm in v4, very stable and smooth. But in v5, it seems like it will take some time again to get to this point and this goes for TrueGlass and RealLight as well.

But: TFDi does have an official Discord server where you can assign yourself a "testers role" and get access to testers channels, if you like. There, they openly communicate with everybody so I think it would help if people with issues go in there and tell them exactly what happened when the crash occurs / give them some logs if possible. They also release fresh builds of the .dlls (RL and TG) from time to time directly on this discord and ask for feedback.

Like I said, they completely recoded both components just days ago, so there will be still issues in it but if everybody helps them, they may be able to resolve this issue faster.
At the same time, it may be neccessary to wait for v5.1 and Lockheed Martin again. It's most likely a small but very annoying and not easy to find bug to nail down..

Discord: https://tfdidesign.com/chat

Good to hear they are working on a fix.

for me when I had bought the 787 a month ago and downloaded it via pc aviator and the update via qw website.

it worked like a charm. And no vram issues Only recently when I had reinstalled P3d v5 I had decided to redownload the qw 787 installer again via pc aviator and the update via qw website, it now crashes.

i should have saved the  previous installers?

would that have made a difference?

thanks

mike

For people experiencing DXGI crash with aicraft addon using the latest beta trueglass, try this workaround, it seems to work with the Maddog:

In P3D5 disable the Vsync in the sim if enabled.

If you need to keep Vsync you can enable  Vsync in your driver setting (in my case NvidiaProfileInspector) but keep this sim option disabled !

Worth giving it a try !

Georges

52 minutes ago, UL612 said:

For people experiencing DXGI crash with aicraft addon using the latest beta trueglass, try this workaround, it seems to work with the Maddog:

In P3D5 disable the Vsync in the sim if enabled.

If you need to keep Vsync you can enable  Vsync in your driver setting (in my case NvidiaProfileInspector) but keep this sim option disabled !

Worth giving it a try !

Georges

Will try 

thanks 

mike

On 9/4/2020 at 2:03 PM, UL612 said:

For people experiencing DXGI crash with aicraft addon using the latest beta trueglass, try this workaround, it seems to work with the Maddog:

In P3D5 disable the Vsync in the sim if enabled.

If you need to keep Vsync you can enable  Vsync in your driver setting (in my case NvidiaProfileInspector) but keep this sim option disabled !

Worth giving it a try !

Georges

That didn’t work 

thanks thou 

mike

I haven’t tried turning off vsync. But for now all is good with true glass off 

55 minutes ago, micstatic said:

I haven’t tried turning off vsync. But for now all is good with true glass off 

I got an email from pc aviator today with the latest 1.3.1 installer available.

and so I tried it and i still get the error with only real light activated.

i had to Disable both.

cheers

mike 

I've been speaking with a certain TFDI developer about this for almost 2 weeks. He's convinced it can't be TrueGlass but P3D itself. Turning Vsync off in P3D helps for a little, but just delays the crash. The only way for no crash is to disable the TrueGlass.dll in the gauges folder. This issue has driven me crazy. I've tried just about everything I can think of. The way I'm able to trigger it the fastest is at ORBX ESKS at the gate with the Maddog. Here's the real bizarre part. It doesn't crash at dusk or at night, even when the dynamic lights are taking my gpu down to it's knees at 15 FPS. No, the crash only happens in the day when I'm running 60+ FPS. Another strange thing I noticed is that turning ON Enhanced Atmospherics helped. I don't usually use this feature, but when it's on, I don't get the crash. Very very strange phenomenon and absolutely frustrating.

55 minutes ago, av8r172 said:

I've been speaking with a certain TFDI developer about this for almost 2 weeks. He's convinced it can't be TrueGlass but P3D itself. Turning Vsync off in P3D helps for a little, but just delays the crash. The only way for no crash is to disable the TrueGlass.dll in the gauges folder. This issue has driven me crazy. I've tried just about everything I can think of. The way I'm able to trigger it the fastest is at ORBX ESKS at the gate with the Maddog. Here's the real bizarre part. It doesn't crash at dusk or at night, even when the dynamic lights are taking my gpu down to it's knees at 15 FPS. No, the crash only happens in the day when I'm running 60+ FPS. Another strange thing I noticed is that turning ON Enhanced Atmospherics helped. I don't usually use this feature, but when it's on, I don't get the crash. Very very strange phenomenon and absolutely frustrating.

When I had bought qw 787 just over a month ago. All was working well.

i had a different issue last week in  p3d  v5 and then decided to reinstall P3d v5 and I downloaded a new  installer from pc aviator.

and that’s where the problem began. I am not able to use true glass and real light without a ctd dxgi device hung error.

apparently true glass and real light was updated recently and they screwed it up.

i had to find out on the forums here .

as tfdi did not get back to me nor qw about it.

pathetic.

art least  if they Responded ide be ok and wait for a fix.

thanks

mike

https://ibb.co/Sf9njX1
 

here’s a pic of the 787 qw working fine over a month ago using real light and true glass beta .

and never came across this dxgi hung error. Ctd

thought ide share.
thanks

mike