Jump to content

[CHK] CTD trying to click OSB for IMP AZ


unknown

Recommended Posts

Hi Deka,

i preordered the JF-17 but only got time to dive into this bird last weekend. This is an awesome module/bird and you did a great job with it, i'm enjoying it very much :thumbup:

 

I got some time now and tried some AG sorties in my generic AG training mission. My first sortie was with 802AKG and went fine. After that i landed, re-armed and refueled with 2 LS-6 and 2 GB-6, after takeoff i launched both LS-6 fine, both hit there targets. After that i wanted to use the GB-6(the version that launches the little bomblets). I powered them on, clicked on the OSB to get into the CNTL menu, weapon was still aligning and i clicked the OSB for IMP AZ. As soon as i clicked that OSB DCS crashed, but it was able to run the crash report app, files are attached but it didn't save the track, according to the log the track was to big. I run DCS in VR and this is my first CTD in the JF-17, i used the GB-6(same version) yesterday without trouble but that was in a short test flight for that weapon and not like today re-arming the GB-6 after i did a sortie with a different loadout first. Yes i did reject/update/load the DTC between sorties. Like i said, this was the first CTD in the JF-17 for me, i used the GB-6 succesfully before, i will have a look if this will happen again and update this thread if i can gather more/usefull informations. I'm running the latest OB, drivers are up to date.

dcs.log-20200324-095720.zip


Edited by uboats

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Thank you both for the quick response! :thumbup:

 

Will check it tomorrow.

In bed now :)

Good night! :D No hurry, this only happend once for me.

 

'AmdPowerXpressRequestHighPerformance' call in log file.

Maybe your video card driver caused something.

But i have an AMD CPU and a nvidia GPU.

I'm no expert but this 'AmdPowerXpressRequestHighPerformance' could be related to VR? I use the "AMD Ryzen Balanced Power Plan" in Windows but the Oculus VR Software is changing this to the "High Performance Power Plan" on startup and the Oculus Tray Tool is setting this back to "AMD Ryzen Balanced Power Plan" after the software is closed.

 

I tried to reproduce this but until now everything is working fine like before.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Thank you both for the quick response! :thumbup:

 

 

Good night! :D No hurry, this only happend once for me.

 

 

But i have an AMD CPU and a nvidia GPU.

I'm no expert but this 'AmdPowerXpressRequestHighPerformance' could be related to VR? I use the "AMD Ryzen Balanced Power Plan" in Windows but the Oculus VR Software is changing this to the "High Performance Power Plan" on startup and the Oculus Tray Tool is setting this back to "AMD Ryzen Balanced Power Plan" after the software is closed.

 

I tried to reproduce this but until now everything is working fine like before.

 

 

I found it in the call stacks of your crash log.

Can not be sure, but it's not seen before, let us do some dig.

 

 

Thank you for report.

Link to comment
Share on other sites

I was flying the JF-17 all week long and had no problems until right now. I was flying my AG training mission again(like every day), this time i started in the FA-18, dropped Mav/bombs on target, returned to the ship, switched slot to the F-16, dropped bombs on target and returned to the airfield, tried to switch slot to the JF-17 and DCS stopped working, i didn't even get into the cockpit of the JF-17. This time the DCS crash app didn't start, i had to cancel DCS.exe via taskmanager, but the dcs.log is attached.

 

The weird thing are these entrys?(and much more in the log)

2020-03-28 12:44:49.151 ERROR   DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_sp_4_normal.dds. Reason: 
2020-03-28 12:44:49.168 ERROR   DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_sp_7.dds. Reason: Requested audio format unsupported.
2020-03-28 12:44:49.170 ERROR   DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_fp_other_normal.dds. Reason: Requested audio format unsupported.

For me that looks like it tried to load textures but was expecting an audio format ???

But i leave it to the experts to interprete these.

dcs_log.zip

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

can you reproduce in latest OB?

 

Both reported crashes were my only CTD's in DCS. But i rolled back my GPU driver from 445.75 and 445.78 back to 442.72 because of strong stuttering in the JF-17 cockpit with the newer nvidia drivers(strangely only in the JF-17). Also after every DCS update i delete FXO/Metashader2 folder and run a repair. Between last report and now i flew the Jeff for some hours(and other modules too) but luckily had no CTD yet again.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...