Luft Waffel

Me (VR) and mate (also VR) are on Enigma Cold War server trying to do some multicrew play. We first load in with him in front seat and me in rear seat - everything syncing fine and any switch changes working between cockpits, performance normal. When I move antenna elevation - no problems. However whenever I move the cursor on the radar screen, it moves a little, jumps back to wear it previously was, and then repeats the original movement that I input. At the same time the front seat is being spammed by "multicrew sync error" messages any time the radar cursor is moved. Manipulating the radar cursor sufficiently accurately to be playable is not possible like this. We then try switching seats, on turning power on and testing radar cursor movement we find that it is synced correctly, no jumping/lagging in the rear seat and no error messages in front seat - but the game performance is completely tanked (~65-75%) fps loss (we initially assume this is just because of other phantoms parked near us). Taking off did not improve fps and neither of us could get more than 15fps when flying. When the rear seater then left the aircraft, the moment he left the fps quadrupled and I was back to normal game performance. Flying a ~20 minute sortie after this I had no performance problems at all. It seems that the multicrew sync - specifically for the radar cursor slew - either does not work correctly and spams errors, or when it does work absolutely annihilates the game performance for both crew members. The only potentially unusual thing I can think of for my setup is that I have two inputs bound for radar cursor slew (one button mapping set for 4-way hat, and one axis mapping for control stick). I have not tested if there is any difference when only having one binding

Strange that it hasn't been fixed/standardised yet given its a problem that's been around for so long and as you say brought up many times. Makes me wonder what this massive chunk of devs they say are working on the "core game" are doing. Surely this can't be such a difficult thing to fix if community members have already fixed it with mods.

All there is notable on event viewer at the time of crash is 'DCS.exe application hang error (event ID 1002)', and then 1.5mins later 'DCS.exe application error (event ID 1000)' which I'm pretty sure is just when I decided I had waited long enough for it to come back and force closed it

I think this may just be from when I finally forced closed the game after waiting for it to come back for 1-2 minutes. The game stopped/froze and I was just staring at the frozen window in the steam VR environment so I don't think that caused the problem. Normally when you force close the game it also force closes steam VR. At the time I was doing a CASE III and trying to connect to the datalink on the ship, as well as flying around the boat to intercept ILS localiser. The D/L wasn't working and it said something like UTM Fail on the datalink screen, I was also out of position for ILS localiser so it could be the moment I got to position behind the ship where I could get D/L some kind of error occurred. This would be my best guess as it's the newest implemented feature I was trying to use. Really I can only speculate

Many of the lights in DCS look very smeared and blurry as the bloom effect is far too severe. The IFLOLS lights on the supercarrier are the main problem as it causes difficulty in actually being able to see its indication. The external lights on the hornet - particularly the nav lights looks terrible from afar as even on the dimmest setting the light smears out across the sky really unnaturally (even in the day!!!). These issues are far worse in VR. When you look at aircraft lights in the real night sky they are literally just dots and you can actually see the colours of the lights which is the point of nav lights as you can tell what side of the aircraft you are looking at from the colour of the light. Please could this be adjusted, I think there are already some mods available especially for the IFLOLS lights but they dont pass IC. Some modules are fine and others like the hornet are unusable. It would be good if the appearance was standardised across DCS aircraft to look consistent and normal!

Very disappointed the game just gave up while I was slotting myself into the marshal stack after an hours sortie. No idea what the cause was - not using any mods. It went unresponsive indefinitely and I force closed it. Logs attached. dcs.20220918-002036.dmp dcs.log dcs.20220918-002036.crash Also for further information the server didn't restart and no one else was kicked out something seemed to just go wrong client side

Would love to see any images of a British Apache without a radome, I have not ever seen this in person or even in a picture. Fully agree with your point about the loadout menu I think that option makes the most sense.

It was an example

If players could add or remove it themselves then it would fix both issues so you're right that would probably be the best option

In a few of the single player missions (eg PG cold start instant action) where the aircraft has the British livery equipped it shouldn't have the FCR removed as the Apache isn't operated in this configuration in the UK.

I think everyone is aware of this and don't get how this changes anything regarding the desired feature explained in the OP; for clients to be able to customise the aircraft configuration

I think this would be the best option, along with it being equipped by default

Having played on quite a few public servers there is disappointingly a complete lack of the longbow radomes. This is because by default the "remove radome" option is checked automatically meaning mission creators would have to go out of their way to specifically change the option themselves to have any apaches carrying radomes in the mission. Especially for countries like the UK that do not use the apache without the longbow radar equipped it takes away one of the main unique features the helicopter is known for. I can think of 4 possible solutions: 1) Longbow Radomes are equipped by default and have to instead be manually removed by the mission creator 2) Radar can be equipped and removed in the rearm/refuel window 3) Radar can be equipped and removed with a kneeboard page when cold and dark (like customising the flare program) 4) Longbow radar is forced onto the aircraft when UK apache skin is applied (When apache unit belongs to CJTF Blue faction) The option to remove the longbow radar when the apache belongs to the UK faction should be deleted entirely as its not accurate for the Apache AH1

Edited to add track replay as requested

Hello, There is a bug that occurs that causes all of the 3D markers to be inaccurate on the HMCS in the following conditions: To replicate this easily: 1. Have a designated target somewhere, the further away the better, since the error in absolute position will be larger 2. Turn on HMCS and look at the target diamond 3. Roll the aircraft as close as you can to 90 degrees angle of bank and hold it there 4. Move your head from side to side and up and down slightly using track IR or VR, you'll notice it most in VR, make sure you keep the markers within the display limits 5. The marker moves around as you move your head, causing its position to be inaccurate unless you look perfectly directly at it Exactly the same render logic bug existed on the A-10C II Scorpion HMD but was fixed very quickly since it was much more noticeable, but the problem is still present on the hornet and F-16. Its harder to notice if you test it using A/A radar-locks, but again its easier to notice on a target further away since the error in absolute position of the target is larger. Its probably also an issue for the DL contacts displayed in the HMD, but its probably hardest to notice there as there is already a lot of error due to the refresh rate which of course is not a bug. Again though, if you try it on something further away you will notice it more. The issue exists for any markers that represent a 3D location in the world. EDIT: Added a track replay - (it should be easy to replicate by just following the instructions though) jhmcsbug.trk