Luft Waffel

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

The first person pilot body was wearing a tan coloured flight suit? Which livery was that with? Very cool!

I watched your video, I have no idea whether that's a bug or if its how its intended to be, but that is not the behaviour I am trying to describe, and what I tried to demonstrate in the track file I attached at the top. If it is a bug you should add it in a separate bug report because its not what this report is about. The issue I reported is not to do with the datalink refresh rate or anything added in the most recent update, it existed before and was the same as on the A10CII before it was fixed in the most recent update. To reproduce STT lock a target at any distance, the further the target the better. You will have the target box in your JHMCS display. Roll your aircraft as steeply as you can and hold it there steady, as close to 90 degrees angle of bank as possible will show the issue most. Then move your head around very slightly from side to side and up and down while keeping the target with in the display FOV. Don't shake your head around massively like in the video just a little wobble. Wobble your head slightly in the horizontal and slightly vertical axis separately but not both at the same time and you will notice as your head goes from side to side the target box slides up and down slightly and wobbling your head up and down slides the box from side to side. If you play on flat screen it might also be easier to see if you zoom in all the way while doing it. It is much more noticeable and easy to see in VR, as it is easier to make small head movements and everything basically seems much larger as it is right in front of your eyes. If you are unable to see the bug it is either because you have misunderstood what I am trying to describe and are looking for the wrong thing, or you are not reproducing it correctly because for example you may not have had the aircraft banked while doing it, or you are moving your head around too much and just pushing the box outside of the FOV in which case the box won't be on the target anyway. In your video you where straight and level where the bug does not occur at all. The issue seems to be caused by the drawing function the game uses for HMDs not accounting for the viewpoint axis not being parallel to the ground. It is a coding logic oversight and needs to be corrected by the coders and won't be fixed by simply running a repair of your game files. I originally reported this issue because it was very, very noticeable on the A10CII Scorpion system and expected the devs to carry across the fix to all of the other HMDs but they haven't done that which is why I reported it again. Datalink contacts and RWR symbols not behaving as they should also doesn't seem right but it has nothing to do with this and is a separate issue that is new unlike the issue I am describing which has existed since the JHMCS was first added. The report was only made now as I was expecting it to be fixed in the last update but it wasn't.

I was having issues with this too, the bullets weren't landing where the CCIP reticule indicated even when using the AGR mode

So the fact that the current behaviour is exactly the same as how it was on the A10CII Scorpion HMCS before it was fixed is intended, and its actually a feature and doesn't need to be fixed? AND this is now just because of the FOV of the JHMCS? Which just randomly decreases substantially as you roll the aircraft, but strangely not when the aircraft is straight and level? AND the radar contact box is supposed to slide around from side to side when it reaches these new boundaries instead of behaving normally? This is how its supposed to be? :megalol:

I am aware that the FOV of the display does not cover the whole screen, and when the aircraft locked is outside the FOV the box will obviously be confined to the display. In the track I do frequently move the aircraft out of the FOV which I understand is confusing but this is not the issue I am referring to. When the aircraft is within the FOV, you can see how moving my head up and down pushes the box left and right and moving my head left and right pushes the box up and down. This is the bugged behaviour that I am trying to describe and what has been fixed on the A-10CII. If you have head tracking or VR you can reproduce this yourself by locking something, or using a datalink contact, or anything that marks a point in 3D space(e.g. not the airspeed or altitude indicators), banking the aircraft a steep angle and then look at the marker while moving your head about slightly. You will notice how the markers shift as you move your head. This was very noticeable on the A-10CII Scorpion but they have fixed it and if you try the same thing on that you will notice how it behaves normally now. The effect is larger and more noticeable at higher angles of bank.

Watch the replay I attached. I explain it in my original post for the same problem on the A10CII: https://forums.eagle.ru/forum/englis...ng-head-around Its the exact same problem, it has nothing to do with the things added in the most recent update, and the issue existed before. As I said, it has been fixed this patch on the Warthog 2, but it seems that the dev teams for each aircraft did not talk to each other and share the fix to be applied to all modules with HMD systems, hence why I'm making the exact same post again in this section for the hornet team to see. Hopefully they can also send the fix to whoever is doing the viper so that I don't have to post it a third time. It is a global issue with the logic the devs used to determine the position to draw the markers at as it doesn't seem to account for the viewpoint not being straight and level if the aircraft is banked. The issue was solved for the A10CII and needs to be applied to all other aircraft that have HMDs.

Hello, Thank you for fixing the bug on the A-10CII Scorpion HMCS where markers where not being rendered in the correct position when the aircraft is banked and the head is moved around. It is in the patchnotes as " Fixed slight roll of the entire HMCS symbology when VR headset is used - it directly affected horizon line, as well as spatial symbols positions " Please can you apply whatever you did to the hornet and viper HMCS systems too, and any other technology in DCS that works in a similar way. It is still bugged on all the other systems in the game except the A-10CII. When I originally reported the bug on the A-10CII section I did also say it was a bug on the hornet and attached a track showing it. If it is necessary I can manually go through and copy and paste this post on the viper section and any other relevant section of the forum as well so that it is noted and fixed there as well. If it is necessary I can attach a track for the viper but the bugs exists in exactly the same way it does on the hornet and did on the Warthog 2. jhmcsbug(solvedOnA10C2).trk

This map uses a lot more RAM than any other DCS map. I have 32GB of 3000MHz RAM and when playing multiplayer in VR on Syria it caps out my RAM and uses 28-29GB :doh: . I don't have any issues on other maps even on the most populated and packed multiplayer missions. The capping out of my RAM results in the game frequently stuttering, and stuttering every time it has to load something new, like looking around quickly or descend rapidly. 32GB of RAM should be more than enough to play a game in VR, and the current RAM consumption is ridiculously high. Some optimisation needs to happen to improve this and bring Syria in line with the other DCS maps, I understand its more detailed but that shouldn't be at the expense of the game being playable on a high end system.

Try it, it doesn't work. The light is solid on both flash and steady modes. I am talking about the position lights and not the anti-collision lights, the ac lights work fine. This wasn't an issue before the update, please fix.

The logic for drawing the HMCS markers doesn't seem to work properly when the aircraft is banked. It becomes worse when the bank angle is higher. I have tested it with the hornet HMCS as well and its an issue there too, but its less noticeable. I will add some replays for the hornet and a10C II. Its much easier to see in the A10C II track. As the head is moved while the aircraft is banked the positions of the markers are no longer accurate and move around depending on how the head is moved. This issue does not exist in straight and level flight, only when the aircraft is banked, and gets worse with higher bank angles. Should be easy to reproduce. I hope you can fix this, players often sit in an orbit around a target and this means that the markers are then inaccurate, this should be an important bug to fix. scorpionbug.trk jhmcsbug.trk

https://forums.eagle.ru/showthread.php?t=258731 "[FIXED]" ������ Problem is that flat screen players (the majority of the playerbase) only effectively have one eye, positioned in the middle of the cockpit resulting in them not seeing angles of the HUD one normally could. To fix this issue, it seems that the view has just been shifted forward to an unrealistic location over the stick so that the player sits with their face in the HUD so they can see all of the symbology. For VR players, who have normal vision and can see all areas of the HUD from a realistic viewpoint, we now have to deal with our face being buried in the HUD by default. What is concerning is that this thread was moved to the wishlist section, essentially sweeping this issue under the rug. It seems to "fix" this, the strategy has been to go from one issue to the opposite and hope no one would notice, hence the move of this thread. This issue has not been solved, only reversed. I hope that this can be solved for all players, perhaps a simple option could be added in the special settings for the A-10 to be able to choose between a VR and flat screen viewpoint, allowing for the best experience for all players. VR is key to the future of DCS and should not be neglected in favour of what may appear more immediately convenient.