Volator

I've been playing a lot of Combined Arms on the F10 map lately. Over the last two weeks a new sort of DCS crash has ocurred to me that I haven't seen before: From the F10 map, when I select a ground unit and switch to external view, the screen suddenly goes black and my GPU cooler instantly revs up to maximum RPM. I cannot exit the game at that point anymore, open up Task manager or anything. Only a hard system master reset works for a full reboot of the system. GPU is RTX 2070, latest driver installed. dcs.log

And the next F10 zoom crash. dcs.log

Next F10 zoom crash log. Did a full repair before btw. dcs.log

@cw4ogden I haven't read through the whole thread, not being an active DCS Mi-8 pilot, but from what I read it appears you definitely got a point there. I think what you have experienced here with the Mi-8 is something that we can see with several DCS modules. Some real aircraft display some certain behaviour, and then the FM developers go and try to simulate it in DCS. So far so good. What I found with some modules however is that this certain behavior is quite exaggerated at times. It appears the FM developers want to make people really notice or feel the special characteristics of an airframe, and they are proud of it of course in being able to demonstrate this in their code, but in doing so they overdo it and thereby get it wrong, so wrong that a real aircraft wouldn't be accepted into service with those extreme characteristics. Sometimes I also think some sim pilots and FM developers think flying in a sim has to feel hard, difficult, otherwise it wouldn't feel real. I disagree with that and think based on my RL (fixed-wing) flying experience flying, controlling an aircraft is quite easy once you learned it. Just like driving a car. First you gotta learn how to do it, but after some time it becomes natural for you.

BTW, I only checked this now, all my liveries in fact are in the folder "Liveries", the folder "Texture" only holds an F/A-18 folder... I don't know where this error message stems from.

Here's an F10 zoom crash event dcs.log

BTW, I talked to other players on an MP server: three said they have the same issue with zoom in F10 crashes.

I see what you did there and I like it The ED forum is basically the only go-to place for me to get information on DCS and the various modules, and I'd be missing out if it wasn't for you to crosspost these, so thank youf for doing so.

Yup, the reported engine fire sounds a lot like engine overstressing. Don't want to make false assumptions here, but there are many people out there who constantly overtorque the Huey because they don't know or don't care about the operational limitations of the Huey. It cruises around 90 KIAS at about 30 sq.in torque. Or did you have SAMs in the area? Or is there a cross binding of controls which could explain the sudden power reduction in your slow flight?

I'm no expert, but here's my experience with that: 1. Target line color depends on target. If you select a unit icon as target, the line is red. If you select open terrain where you suspect a unit, the line is white. 2. I think this is related to 1 - at least sometimes if you select a unit icon as target, it's sometimes impossible to remove the target... no idea why. Sometimes double-clicking helps 3. Beats me, but I experienced the same. Sometimes it helps to jump into the unit and then leave it again, sometimes it doesn't. 40 is the maximum number of rounds for the M109. 4. Same as three. I think it's safe to say CA is quite unfinished and bugged in it's current state, which is sad as this is a module with a tremendous potential in DCS. Currently I spend most of my time on MP servers in Tactical Commander slots, it's great fun in persistent online wars!

Latest game crash log file, not F10 zoom related though, but being in F10 map. The log file is incredibly huge https://www.mediafire.com/file/makeel33p7hd0tm/dcs.log/file

19.1 Maybe with the option to display the in-game callsigns (Enfield 11) instead of the sometimes really weird user callsigns. 21. ATC/GCI style mode for F10 map displaying callsign, altitude and speed next to the icon.

20. Optional event markers for units, audio and/or text, informing tactical commanders that a unit has spotted enemy or is being engaged, with a button that moves F10 view focus to that unit

Here it is. dcs.log

Thanks for having a look at this, here you go. The date of the file says it's from 18th May, which is before those crashes started - it basically happened with the latest OB patch. dcs.log-20210518-150308.zip

Those new ground units (La Combattante II and the Leopards especially!!!) look fantastic. Well done ED!

Is anyone else experiencing this? On a multiplayer server working a CA slot, after playing for 45 minutes or so, DCS regularly crashes when I zoom in closely on the F10 map.

13. Artillery fire missions should not automatically be deleted if they are assigned/linked to a spotted unit on the F10 map that eventually disappears because it is out of LOS for spotting unit. Arty should keep firing at the last known coordinates, if the unit was static. 14. Option to deselect fire mission targets being tagged to units if target marker comes close to them, I'd rather be able to place the target point individually 15. Option to create groups from individual units "Command and Conquer-style" to move units together or assign fire missions to arty with one single click. 16. Option to save groups, assign names, recall them via menu and option to automatically move focus on F10 map to group

Yet another good heli server is, as the name implies, the "Rotorheads" server. It's persistent PvE and also features a good integration of Combined Arms (four Tac Commander slots), which I think is a core feature of good heli servers (i.e. the air to ground integration). The enemy AI ground units seem quite clever. Very target-rich environment though, needs a dedicated team in the air and on the ground to be successful.

PC, please consider adding an autopilot "cheat" for the SA-342 and the OH-58D, similar to the one in the UH-1 Huey module, that can hold altitude/heading and rules out steering inputs. The current autopilot modes on the Gazelle are all good tools, but with a stick that isn't self-centering (like a TMW with a 45cm extension), you can never let go of the stick because it will override the autopilot modes. I know it's not a realistic mode for the Gazelle and possibly not for the OH-58D, but it would make the life of a sim pilot easier.

Hi, suddenly I can't control the Viviane sight slew up/down via axis anymore. Tried two different axes on two different devices. Slewing left/right via axis works on both devices, axes are functioning in controls menu, are assigned, no interference due to other axes assigned... and via keys slewing up/down also works. Track: https://www.mediafire.com/file/qwku3k7vm9isytk/Through_The_Inferno_SYRIA_v2.1.2-20210516-200625.trk/file Track shows a MP mission, also tried in SP but forgot to save track. ***Edit*** Problem solved. For some reason under "Special" the option "Second joystick for camera" was deactivated. That was the culprit.

It seems this is rather hardware-related.

Here's another track from an MP server that shows ground units getting lost and stopping to move. Changing formation usually gets them moving again, but they often travel off path and get stuck in trees or buildings. https://www.mediafire.com/file/zv1qos1ll8vd8ly/Op+Be+Quick+or+Be+Dead+v4+MAY2021-20210512-204626.trk/file

Good news. Remember how users received heavy flak from some individuals in this forum for pointing out some oddities with pitch behavior pre 2.7.

Thanks ED, good thing!