Crispus

Have you tried the repair option? I don’t have a link but if you search DCS repair then you should get plenty of good hits.

I think what the asshats like me are saying is that getting upset isn’t going to change the practical reality for you. Angrily telling professional software developers that ideally their product should ideally be 100% stable and bug free isn’t constructive, they already know that. The problem is that every other post on here is a complaint that they aren’t releasing their unstable code base quickly enough.

Caveat Emptor. You paid for precisely what was available at the time of purchase. The engine is free, you bought/buy modules having received, and presumably tested, the base product for free. If you thought that it was bad then why did you throw more money at it with the hope that it would some day meet your expectations? This is entertainment, if it doesn’t entertain you then do something else. Time is precious, it’s not worth getting this wound up about a video game.

I have seen a few complaints about the ladder on the Hornet in MP but no solutions I am afraid. I naively thought that they meant the pitch ladder on the HUD:music_whistling:

You could check out the Grim Reapers Tutorials on YouTube. Playlist for each aircraft starts with a video on mapping controls. The guy who does the videos uses an x56.

“A Swiss aerial display team has performed a fly-by over the wrong town, surprising people at a yodelling festival taking place nearby.” https://www.bbc.co.uk/news/world-europe-48916084 “...the F-5E Tiger II aircraft were not equipped with GPS technology.”

Another +1 here. DCS has re-defined my view of what a consumer simulation can offer in terms of detail and fidelity.

So you can’t designate the HARM display to be Sensor of Interest? You are able to switch SOI between the HUD and other displays though right?

Does it always pull to the left? If so it could be a sensor fault in the base of the stick. I would imagine that would be a factory repair/replacement. I have had control input freeze on me in the past, in that case no other inputs worked either. When this happens, do you still have control over all of the other axis and buttons on the warthog?

This could also be the best fun an FAC can have in DCS.

Interesting article from ArsTechnica: https://arstechnica.com/tech-policy/2019/01/previously-secret-cia-report-documents-spear-attack-against-surveillance-plane/

I have both Tacview and Viacom Pro installed, would you categorise them as mods? Otherwise vanilla 2.5.4

For the logs attached in the post above I was taxiing at Kutaisi in the F18. Once crashes had happened I was able to close DCS with ‘end task’. Earlier I had two hard lockup’s while in the F10 menu while attempting to get some value for money from CA. In that case I couldnt force quit DCS with end task so had to log out to close it. The logs from those crashes were corrupted.

I am getting crashing every time I play at the moment. Have attached 2 x dumps but must have had 5-6 crashes this afternoon. In many cases the dump archive is corrupted. I dont have any mods accept for Tacview. NVIDIA driver is 417.35, other spec's in my signature below. dcs.log-20181221-160239.zip dcs.log-20181221-172730.zip

Yep, this helped enormously. Hadn’t realised that the RWR needed to be turned on...:thumbup:

Thanks for the advice, went back to the mission and waited it out for the SEAD to do their job. Worked a treat.

No, I don’t expect to dodge the missile based on the sound of it coming for me! I am just saying that in other aircraft I generally hear the missile detonate and feel the aircraft move as a result before I start to lose control, or get switched to F2 view. Maybe it’s just me. Thanks for your advice though, it’s all good.

Thanks, I Will do! However it’s not so much that the RWR didn’t go off that bothers me. It’s more that I rarely, if ever, hear or *feel* the missile detonate immediately before beginning to crash and burn.

I am pretty new to DCS and am getting hours under my belt. I mostly fly the F/A-18 but also have some time in the AV-8B and a couple of other aircraft. I am painfully aware that my situational awareness sucks but it seems to me that when death comes (and it comes frequently!) it all happens rather quietly. I just flew the F/A-18 Interdiction mission and got shot down by an SA-3, I had no RWR alarms and when it blew my right wing off I heard and felt no impact or explosion. Just started barrel rolling towards the ground. My unscientific observation is that in other aircraft I get more ‘feedback’ when I am being shot down. I have also survived the odd hit in other aircraft which as far as I can tell has never happened in the Hornet because I generally just suddenly switch to F2 view and watch myself crash and burn (which is a bit jarring in VR!) Should I expect to hear the munitions which kill me?

The 9600K is pretty good. I replaced my 4670K with one last weekend (but on a Z390 Motherboard and the some 3200MHz RAM) and it made a decent impact on overall performance. Overclocks to 5GHz easily with a H80i water cooler. I would agree about the graphics though, a 1070 would be a minimum for VR in DCS for me.

This sounds related to a problem that I have with the same mission using VR. https://forums.eagle.ru/showthread.php?t=224221 If Fly Again is used then the view in VR jumps around and then gets locked so that head movements are not tracked and viewpoint is fixed straight ahead. It’s very disorienting! I don’t have a fix, other than to exit back to main menu before going back into Instant Action.

I have the same issue but i only seem to be able to replicate it in the AIM9-X instant action mission. Have tried the F18 in other missions with and without JHMC and/or AIM9-X and don’t see the same problem.

No, you can’t skip it but you can fast forward: Ctrl + Z <- To Accelerate time Shift + Z <- To reset time acceleration Alt + Z <- to slow down time

I have reached something of a resolution. In short, 'Use Mouse' needs to be turned ON in VR settings. To explain, I had 'Use Mouse' set to OFF because I didn't want my physical mouse to interfere with my interactions with the cockpit when using the VR viewpoint reticle (blue cross) and the mouse buttons on my HOTAS. This configuration works absolutely fine when the pixel density is set to 1.0. If the pixel density is set to above 1.0 then the very first interaction that I make with the cockpit causes the freezing that I reported above. With 'Use Mouse' set to ON then the freezing doesn't happen when pixel density is set to above 1.0. From my perspective it is perfectly acceptable to leave use mouse turned ON and so I would say that the problem is resolved, but I am still curious about why it happens!

I went back and did a bit more testing. The problem is definitely initiated by interacting with the clickable cockpit. I flew around for several minutes and cycled through options available from my x52-pro HOTAS and everything was fine. As soon as I clicked on the A/G switch everything locks up. After that I cannot interact with the cockpit with the mouse, and all keyboard or x52 inputs are ignored. I would upload a track to illustrate, but can't because the only way to get out of DCS after this happens is via ctrl-alt-del so the track is never generated or saved as far as I can tell.