Islari

Bug: On a Winwing Orion 2 F-16EX stick, when engaging the paddle switch to button 8 (full paddle deflection) it paralyzes the input device button, only the axis continue to work. I have to go back to ESC menu, CONTROLS and press one random switch to unblock the switches. The behavior appears whatever binding is linked to this hotkey. Why do I post it here ? Because it only do this with the F-14 as a pilot, I use it as RIO as modifier and everything works. I checked if this button might be link to a bad control on every other item of the list, it is not. Can I reproduce it 100%: 100%, evey times How to reproduce/ description: Step1: Get a Winwing Orion 2 F-16EX stick Step2: On F-14 Pilot control page, bind the button 8 to any control. Step 3: Press the button while flying Result: Every button of the stick become inactive DCS Version: 2.9.18.12899 (but was already acting like that since 2 months approx) System Specs: CPU: AMD Ryzen 5800x GPU: NVIDIA RTX 3080 RAM: 32GB RAM SSD: 1x M2 1tb; 2x 2tb OS: Win10 Peripherals: Joystick: WinWing Orion 2 - F-16EX Throttle: Winwing Orion 2 - F-15EX Pedals: Winwing Orion 2 - Skywalker Others: Winwing Orion 2 - MFD Headtracker: AItrack + Opentrack (bug is present with or without) Mission File: Every flight Log: No particular log Track: Not see-able trough track Video/ Screenshots: Will add if necessary Mods: I do not use any mods except SRS and Winwing MFD link. But bug do not rely on these as I tried vanilla

dcs.log-20250725-161300.zip Update with an immediate action F-14B on CV-59. Crash when wire trap

Got the same issue, but not only with F-14, F-18 and F-4U. Tested on CV-59, 71, 74, 75, 11. No waveoff related or something else, it crashes when catching the wire Using OpenTrack Will upload a crashlog soon, but interestingly this does not affect a friend with Tobi Eyetracker Game in vanilla, except Winwing hooks for hardware

Hello Zabuzard I'll try to find a track to share with you Just in case about the slight move we generally perform the alignment while chokes on to prevent this problem, so no move intended.

Hello, It's been multiple times that the INS align process is completely bugged. I follow every procedures found on the manual, and the issue also happened during the WSO Cold Start tutorial. It seems that the ALIGN light never goes blinking when the issue happens, I waited over 30 min with a steady align light in the tutorial (so you can assume every steps were perfects as it is guided at least for this example). I finally switched the INS knob to NAV and it seemed to have validated a BATH alignment at least. Sometimes everything works as intended, but sometimes not, with the exact same procedure.

Since last update I've encountered this problem many times, every time my pilot get shot by a round (not explosive or missile) my game immediately crash

The refuel guidance lines are wrong for everything but F-16. They've been made by ED for it, not for the others planes It's an ED side wishlist to be made

This is clearly not HB fault as we've seen flying a pretty build of the F-4 for few days on content creators screens. You know how HB could just become the best add on creator ? Giving everyone (who has preordered it) the same key as the content creators. As mentioned before by someone else, I am one of the guys who took one day off, so this last minute mess will gonna cost me around 200$. If they had told us that delay before, we could have canceled our day off.

dcs.log It seems to come from DTC or The Way Ok, it's DTC dcs.log

OK this time it worked ! I have deleted every scripts hook and liveries from my install. Can't figure which one was harmful, and I hope this is not the Quaggles commands because I really need this one dcs.log

@Lord Vader Well, I deleted all mods, deleted fxo and meta.. again. I repaired the install to make sure that there is no mods left It's better, but not perfect. Now 30% GPU use, I get about 25fps on 4YA Caucasus I only let SRS and TACVIEW because.. well everybody is using those ones I would not be the only one to get this problem Here is the .log: dcs.log

Hello, For the driver part you're right, it's updated. For the FXO and Metashaders2 it's already done too, first thing I did. I'll try the delete mods things

Sure it has max owner plan since years. The thing is that this problem is only when piloting F16 in MP. Every other aircraft is ok Just to be sure I went to my powerplan to verify, it was well set

I just figured out something while trialing the F16, When I go on any server, my F16 performance are horrendous , I get like 5fps. After some check, it appears that the GPU is not activated and does not provide any calculation (GPU at 0-5%) As soon as I jump in another aircraft (M2000, F18, F15E, F14B), GPU starts to work and everything is ok (60 to 100fps depending on the server and people connected) It does not happen in solo, everything is ok on this side (100 to 120fps). Does not depend on map selection, same behavior is observable with every map (-+ some fps due to usual map which take more resources) My sys specs are: CPU: Ryzen 5800x GPU: RTX 3080 RAM: 32go 3600mhz Indeed I tested to delete the module then re installing again, then I proceeded to a DCS full repair (with and without the module installed) Added last log and track files where a crash happened Legend for the picture: Image/s: FPS Utilisation de l'unité centrale: CPU use Utilisation du process. graph: GPU use dcs.log Tacview-20240505-224855-DCS-Client-4YA_Syr_PVE2_V2.46[04_MAY_OVC_RAIN].zip.acmi

Nothing un France yet. Did you received some mail to announce the shipping + tracking number or it was complete surprise ?