unknown

Did you activate the CLSP on the AAP Panel to your right? I have no problems with the TPod after a cold start in SP, didn't use MP much myself. Edit: Stupid typo, CLDP not CLSP :beer:

There is a second option, if i remember correct it's under the game options and it's called something like avionics language. Set this to english, if this is set to native(or something like that) your Abris is still in russian.

+1 That was a pleasant surprise :thumbup: :beer:

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.

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

The forum software doesn't allow to upload the .log file, just zip it.

After some time without the Viggen i tried this module yesterday again in the latest OB version. I did a hot start on the runway and was thumbling with my hotas to find out what i had mapped and was greeted with DCS stopping to work, not a CTD with track and log.... It just stops working and i have to kill DCS.exe with the task manager. I jumped in another module after that experience. Today i tried it again with the same result, i figuered if a activate the radar on the runway and press my mapped keys for the auto pilot a couple times DCS just stops working. Attached is the dcs.log file. dcs.zip

Just enable the english cockpit under the KA 50 special tab, no need for a mod for this.

This is fixed in todays patch :thumbup:

Strange, even with the performance hit/bug of 2.5.6 i get 35-40fps(locked) in VR in the Viper with higher settings than you, and way higher in 2D.

Hm, this friday i didn't receive an e-mail Newsletter too, for the first time on my end. Every newsletter before that i received by mail, nothing changed on my side, i'm still subscribed and the newsletter is NOT in my spam folder....

I don't know if you use steam or stand alone, i use stand alone. And in that version i had a marking of 2 new modules in the main menu of DCS, i clicked on the module manager and it told me i could install both modules, i canceled that becuase i already own FC3. I can't speak for the steam version but if you are using the stand alone version you have to accept the modules in the module manager and only then DCS starts to download them! And the only mapped keys DCS ever overrided on my side were my HOTAS commands with DCS default ones. And considering you are the only person here on the forum having this "problem", yes it looks like a problem only on your side. But he, it's always the others fault, right? :lol: ;)

Yes, got mine yesterday 16:17.

LoL, you get them to test them this weekend if you want to, after this weekend they disappear and you can buy them if you liked them and want them, if not nobody is charging you for anything. They did this with the F-18 and the F-14 also, people liked it because they could make a picture of the modules themselfes. Never heared that modules messed up shortcuts if you don't use the modules, must be a problem on your side/install?

Nice to hear that you will take your time checking future updates internally for a longer time. :thumbup: I wonder how long it will take before peaople are complaining that you need to long for patches because you test them.... :lol: SCNR ;)

I use the stand alone version not the Steam version, but i can't see this thing and i'm using only VR(Rift S). Here is a link to a different bug report i did about a different problem, it was recorded using VR and there you can't see the problem you have. https://forums.eagle.ru/showthread.php?t=264281 If you have a fast internet connection i would suggest you uninstall the KA-50 module, delete manually every file left(KA50 folder) and reinstall the module because you mentioned you used the VR shader mod. I believe(don't know) this is the root of your problem(a leftover file...). I hope you can figure it out!

Hm, i'm using the Rift S also and never saw that square, very strange. Edit: Which version are you running, Steam or Standalone? A screenshot of your options? A Track, i don't think it will help but maybe?

Yes maybe YOU should do this ;) Your report is from 02-21-2020, 05:28 AM and my report is from 02-20-2020 06:18 PM :music_whistling: :beer:

Hi Gizzy, i don't know if you tried it already but your "light problem" is linked to your shadows setting "flat only", if you switch this setting to low or higher the button light is working fine, as soon as i set this to flat only i have the same problem as you have. Not sure if this should be posted in the bugs section or if this is WIP :dunno:

Could you try changing your shadow settings from "flat only" to at least medium? Would be interesting if that setting is "your issue" :beer:

Hi Gizzy, here is what it looks on my end. Could you post a screenshot of your settings? Attached are mine. I noticed in your video that your cockpit looks extrem black, for example left/right console near the rudder pedals. I don't know if this is a YT thing but on my sider thats not like that. Here my test, should be 1440p soon.

This is how it looks for me, hot start, if you press that button you can see the light turns on. But i think the problem is if you have direct light on that panel, then you can't recognize if it is turned on or off. Not sure if bug or feature? In RL it's hard to see some lights/LED's with direct sun light on them.

This time i did just the install without deleting the metashader/fxo folders and i did not run the repair after the update.

Thats not how it is on my side, if i push the auto turn button "the light goes on" not off like on your pic.

Or it's a problem with the english cockpit, hot start on PG on Burj Al Arab heli pad and Auto Turn turned on EDIT: No, works also with the english cockpit.