F15E Backseat is not rendering properly after latest 2.9 patch

[RedHot]

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

[draconus]

1 hour ago, RedHot said:

When I move to the back seat...

Do you use dedicated key bind or just move the camera back?

[RedHot]

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.

[draconus]

I suspect some mods. Please rename temporarily the \saved games\dcs folder and run the game.

Also try DCS repair. Upload your \saved games\dcs\log\dcs.log if still having trouble.

[RedHot]

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.

[RedHot]

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

Edited December 16, 2023 by RedHot

[draconus]

You're still running with mod.

[RedHot]

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.

[draconus]

Thanks for the feedback. I could reproduce the "issue" playing your mission and fix it by removing the action or the whole trigger.

Why would you use this command anyway?