RedHot

I have the same problem. Transporting troops and disembarking them works just fine. However, they assume RED state when disembarked, and will not move to their designated waypoint. I have tried to push their state to Green before they embark the transport, but this did not work. This is super anoying, as it kills all realism in my missions. Would be really great if someone have a fix.

It happens across multiple missions and maps -Nevada and Kola Random failures in game settings, is not checked The debriefing does not indicate spesific damage or fault. When it happens, I loose all flight controls. Neiter stick or rudder works, meaning the cockpit freezes

This started to happen lately, and semes to a random thing. Without warning, the F18 starts behaving strange during missions. It could be oscillating movements, or just rolling over violently. When this happens the FCS system just does not work anymore, so I cannot correct anything. It ends up with me crashing, without being able to complete the mission. Is this a bug with the new FCS model, or am I doing something wrong ?

I have put together a Moose script using the Fox Moose class. This works just fine. However, I wanted to add the scoring class to the script, so I get a score when I evade a missile, and a negative score when the missile is destroyed close to my jet. I almost managed to get this to work too, but got stuck and need some help. I use the OnAfterMissileDestroyed event function to assign the negative score when the SAM is destroyed close to my jet. This works fine. However, I cannot figure out how to capture the event when the SAM self destructs after being evaded, for assignment of a positive score. Hopefully someone have had the same issue, or can offer some insight which can help me solve this problem

So guys, finally got this resolved. Thks for chipping in. This is what made the trick 0. Unchecked the "Enable VR" box in the DCS VR settings tab. (I had to start DCS in 2D using the --force_disable_VR argument. Otherwise DCS would chrash after the NVIDIA prompt) 1. Closed the Oculus app (The new 63v of the app is creating a lot of problems for Quest users and are preventing DCS from starting. VD is the easiest workaround) 2. Removed all "--force_oculus, --force _VR arguments from Steam and the desktop shortcuts 2. launched VD (Quest3 codec, VDXR runtime) 3. Opened DCS in headset from Steam, selecting the "open in MT Oculus VR Mode" option PS. Only issue I have not got my head around, is that although I select the Quest3 Codec in VD settings (PC), the Codec in the VD game overlay shows HEVC. So for some reason VD changes the Codec when DCS starts.

Hmmm. Interesting. Will try without the «—force_oculus_vr», and revert. Here is a perspective: I have set VD to run VDXR and to use the Quest3 codec. I understand from all the videos out there that the entire point is to avoid SteamVR. This semes to be working just fine. VD launches and the imagery in the Quest3 is absolutely fantastic. So, I recon that the problem must sit with DCS and not VD. In some way I have to be able to tell DCS to start in VR mode -inside of the already exsisting VR which VD is streaming to my headset. What confuses me is that DCS launches just fine in VR mode, when I use the QuestLink app. However, then I miss out on all the benefits of VD and VDXR. PS. I have installed the Oculus Tray Tool, and I have checked the «Enable VR headset» option in the DCS VR tab. I have not installed the openXR app.

I just bought my Quest3 headset, and got all to work fine with Quest link -cable. However, I also installed Virtual desktop, and started to explore the new features there. It lookes like VD can boost performance, so I decided to use VD with the VDXR runtime instead of the QuestLink app. I use the Steam version of DCS. But when launching DCS in VD with the VDXR runtime, it stays in big scree mode. So the game launches just fine, and I can start a mission, but it does not go into VR mode. It sort of stays in the VD app, like I have it on my physical screen I have tried to launch DCS from the VD game menu, from the Steam app in VD and from a MT shortcut on the VD desktop. I have also tried to add --force_enable_VR --force_oculus_VR to the path in the shortcut, and in the steam properties for DCS. So, I am running out of options here. Semes really strange that something so good as the new VD with VDXR does not work because the game only stay in "big screen mode". Any help on this comes highly appreciated

ok guys. I verified the installation using the steam file verification feature. After that, the game started. So, I guess it was some files which was corrupted during the download -most probably the GraphicsCore.dll.

1. I am not running Oculus VR on my PC 2. There are no log files. Does not look like the log file has been generated. Application terminates before any files are read or log is generated 3. I tried to start from Steamapps folder. I got error message below. Looks like there is something wrong with the Graphics. I did update to the latest version of the NVIDIA driver just before I downloaded the DCS update. I have a NVIDIA RTX 3080 graphics card.

Does not look like the log file is generated. I cant find it in the saved games Log folder. It looks like the game terminates before it gets to read any files and generate a log.

I have the same issue. I select one of the options -VR, MT, STEAM, and the button goes blue and shows "stop" as normal, bet after a second it turns green and shows "play". Game doeas not start. Hopefully someone can help here fast. Otherwise the entire weekend will be ruined

I have the same problem. Tried to bind the video contrast and brightness nobs to an axis. However, there is no video hud contrast and brightness axis in the axis bind view. So, help......

Better and more animated infantry Animated ground crew An undo function/button

After spending half saturday re-creating the mission file which causes this problem, I finally found the problem. It turns out that I am using a divider in the trigger list to make it easier to group the various triggers. I use a notation lige ++++++++++++ BDA Score +++++++++++++++. The conditions are empty, and I put the "Begin acting player (1)" statement in the ACTIONS. This is something I picked up in a youtube video. It turns out that this is the line which is causing the problem. I deleted the trigger, and then everything worked just fine.

Tried to repair, by running the Steam verify files function. It did not work. Same problem. The backseat is not rendering properly and the viewpoint is in the back of the helmet of the WSO. I have attached the log below. Looks like it is a problem with this spesific mission. I tested using instant action, and a different mission on the same map. Then the WSO rendered properly. So, what could it be which is isolated to the mission file which creates this problem. The mission file is attached below dcs.log F15 NEVADA M0 Low Level SEAD.miz

Thks bud. Good call. I only have one mod installed, which is the Massun92-asset Pack. I'll try a repair and see if that works.

I just move the camera back, using the standard keys for moving the viewpoint. Switching to the backseat and front seat, I use standard 1 - 2 keys. I did map a whole bunch of switches and buttons for the backseat sticks, to my Hotas, but none of these work, as there is no stick and throttle rendered in the backseat.

Hi After the latest patch, the backseat is not rendering properly. When I move to the back seat, the camera view is behind the WSO, so I see into his oxygen mask. When adjusting the camera, the backseat cockpit is only 30% rendered. So, no stick, no MFDs, no switches etc. This makes it impossible to fly this wonderful bird, as I need to jump into the backseat to switch on the TPOD and the TEWS. I am reaching out to the community after having tried to fix this for some time, without any success. Any ideas or pointers comes highly appreciated. PS. I run a HP Omen with an i9 processor, 2TB SSD disk, RTX3060 card and 32 MB RAM

Hi guys I am using Steam for DCS. Are the F15E patches from Razbam included in the Steam patches, or do I have to get them from somewhere else ?

Joining the crowd here. Same problem. I am trying to bind the INS nob, the JTIDS nob, the NAV FLIR switch and the Radar nob to keystrokes, and then using voice attack to operate the controls. However, the bindings does not work for any of these. One thing I have observed trying to troubleshoot this, is that when I click on the INS, JTIDS and RADAR nobs with the mouse, it looks like the nob is slightly pulled up before it is turned...... maybe this is the reason it does not work

I have been using cockpit parameters for a lot of triggers for the F16 and F18. Now I need the list of cockpit parameters for the F15E. Spesifically I need the argument and value ranges for the holding/parking brake. Anyone ?

Thks a ton Sedlo. It worked

Hi I have used the COMM1_FREQ parameter to trigger activation of missions for the F16 and the F18 modules. However, it does not work for the F15E module. Does anyone know what the Cockpit Parameter for the two radios in the F15E are ?

I looked up the Vive controller bindings in the DCS controls tab. It did not have any axis bindings. Tested again, but no joy. However, I found out that it is only the left hand controller which is the problem. When the right hand controller is on, and the left is off, everything works just fine. When the left hand controller is on, the stick starts flickering again. After checking that all Vive bindings in DCS were deleted, I starter testing bindings set up in steam vr. I stripped out everything from the DCS app spesific binding configuration (only left grip laser pointer and trigger click). This did also not fix the problem. Then I did the same stripping of bindings for the Steam VR app and Steam Home and VR Dashboard apps. Same result. No joy. So far, it is clear that the problem is the left hand vive VR controller. Something with its configuration is messing with DCS, and makes the stick flicker and the game unplayable in VR. please help.......... PS. Flying the Hornet using a Thrustmaster Warthog Throttle and F-18 stick

Done some testing on this problem and found that the left VR hand controller is causing the problem. If I turn of the left controller and keep the right one on, there is no flickering when moving the hotas stick. I created a custom binding for the VR hand controllers using the steamVR settings, with a bear minimum of bindings -just the trigger and the grip. However, it still seme to be the left controller causing the problem. I see some of u are talking about axis bindings. Is there anywhere in DCS you can set bindings for pointing devices ?