RogueSqdn

@BIGNEWY thanks for the response, didn’t want to get home and be disappointed.

@NineLine at work so can’t check till much later. Saw the hotfix announcement with some QAG fixes. Is the Germany issue still present?

I haven’t just let it sit, but FYI the stats in my sig are out of date. I now have a 285 Ultra, 5090 FE, and 128 GB RAM. DCS is on its own NVME.

@NineLine I have seen it happen with both having the icons present and having them not visible.

I got an antiship mission to load with the Viper, but it ended after about 3 seconds with some message about a time limit that I didn't have time to read.

What aircraft are you using? I used the F-16 and have Air, runway, parking from hot and cold.

In trying to fly a generated mission in Germany (SEAD, F-16), I continually get stuck at 94% when trying to load the mission and have to force DCS to quit. Missions with no ground targets seem to work though.

Edit your flight group. There will be an option for ground starts.

Reinstalled PimaxPlay and have the 566.14 nVidia drivers. I was able to get into a mission this time. I don't know what made the difference, but the log posted above shows nVidia 566.03. I'll mark it up to graphics drivers.

@BIGNEWY Sorry, just now saw the updated posts. I'm not overclocking at all. I generally stay updated with release nVidia drivers (using 3090 FE), and believe I've updated since the last post. I currently have my Quest 3 hooked up, but I'll hook the Crystal back up this weekend and see if it works this time. To answer the other posts questions, I did not have OpenXR Toolkit installed since its functionality was added natively to Pimax Play. I currently have it installed for using fixed foveated rendering with the Quest 3, but plan to uninstall it before trying my Crystal again.

Trying to get my Pimax Crystal back up and running after a while of not using it, but I can't for the life of me make it into a mission without the game crashing. Can anyone help? Thanks! dcs.log-20241103-214314.zip

I think it’s renaming my vJoy devices and causing conflicts. What happens is I click launch DCS and it just never gets to the menu.

I'm at a loss, here.... I can't get to the main menu. dcs.log

@BIGNEWY getting the error, have purchased entire map. null dcs.log

Having trouble with the IFF master knob on the F-16. I can move the knob but not get text labels out of it. I just get a value of 1.0 returned, no matter what position the knob's in. I've tried both 539 and 540 as the DCS ID in the Title Text section. nullnull

@Wostg any way to get channel numbers in the comm windows without the asterisk? That causes them not to work.

I had copied them from elsewhere in the file. return ufcUtils.buildSimAppProUFCPayload({ option1= ChaffCount, option2= FlareCount, option3= Altitudes, option4= "B" .. HeadingString, option5= Fuelpercentage, scratchPadNumbers=scratchPadNumbers, scratchPadString1=scratchPadString1, scratchPadString2=scratchPadString2, com1=UFCL06NoSpace, com2=UFCR07NoSpace, selectedWindows={} }) end No chaff/flare issues yet with what I posted. Will keep in mind what you posted.

@Wostg I've managed to get chaff on line 1 and flare on line 2 by putting this in the body and changing all the 99 references to 999 (since chaff default is 120): local ChaffCount = "C" .. Chaffdigits local FlareCount = "F" .. Flaredigits and this at the bottom: option1= ChaffCount, option2= FlareCount, I've tried what you listed for Com1 and Com2 but get no results. EDIT: Your suggestion works, idiot me didn't have commas after them. ufcPatchF15e.lua

@Wostg Just got the F-15E working. Thanks for your work! However, I'd much rather have the comm digits in the windows next to the comm knobs, and maybe the chaff/flare count in the first option window. Looking at your LUA file, I'm not sure how to accomplish that. Could you guide me in the right direction, please? Thanks!

I've been having massive Lakenheath flashbacks lately due to this module. Sometimes that's a good thing, sometimes not. But when it involves this jet (and not other things), it's good.

Been having FCU problems and had to go back to PointCTRL v1 FCUs (and associated smaller FOV). Just hit Buy it Now.

I typed this checklist myself. It includes plenty of things that aren't modeled yet but is based on the real thing and in the same format. I also extracted the last few checklist pages from the manual and converted everything to PNG so they could be used in DCS as your kneeboard. Enjoy! F-15ESE.zip

Been searching for F-16 panels with no luck

Hover over them, sometimes you'll get a tooltip explaining it. There's two possibilities: 1) The same joystick button or keyboard command is mapped elsewhere. Since you're showing the Hornet module, check the UI Layer. 2) A device you've assigned a modifier to is not connected to the PC.

My experience with Razer gear is that if you have too many of their devices plugged in simultaneously, it can cause other HIDs to disconnect. How many Razer devices do you have connected now? Funny business usually starts around device #3. I have three currently: The Leviathan v2 soundbar, the Deathstalker v2 Pro TKL keyboard, and the Basilisk v3 Pro mouse. However, since the mouse and keyboard both connect to the same dongle, I only have two actually plugged in. If you have a wireless keyboard and mouse from Razer, I'd recommend seeing if they're compatible with "Hyperspeed Multi-Device Pairing." List of compatible devices: https://www.razer.com/technology/razer-hyperspeed-wireless