Nealius

Ease of manufacturing.

I'm using the Q2, not the Q3, so I'm unsure if a Q3-specific cable would even work. I couldn't find Stouchi brand on Amazon Japan, but I did find a few cables using "fiber-optic." The Amazon here seems very picky with search terms. But they still have the same 5Gbps transfer rate.

I see no "optical" USB cables existing in my region's Amazon market. This issue also appears to be linked to any time DCS causes some kind of performance spike. I've now had it crash while loading into multiplayer before I get to the coalition screen, and I had it crash when opening a mission file in the Mission Editor.

Aren't the Meta cables extortionately overpriced?

Anker USB 3.0 cable, 5Gbps data transfer. I have two of them and this happens with both, but it only happens when clicking "join coalition." I need to see if I can monitor my PC resources and see if DCS is causing some kind of spike when clicking "join coalition" because that action is the only trigger for this issue.

IIRC the hook has a 450kt limit but we know in practice that was regularly exceeded during SHB. Especially with Nasty's 600/600 SHB.

Your premise relies on 2014 civilian regulations being applied to 1975-2006 military use, and it still doesn't address the empirical facts regarding G tolerance of the human body or of airframes. To strengthen your argument I suggest you detail what those "safety reasons" were.

"Can" does not mean "should every single hour of every single day of every single season." DCS strives to simulate what is true the majority of the time, not what's shown in one or two pictures. This is inconsistent with the approach taken with everything else in the sim.

I believe it may be related to this other issue as well, because I've seen the dancing uncontrolled AI simply vanish completely after they do their dance. It only seems to happen with certain aircraft, though. So far I have observed it with the A-10, E-2, Mi-8, but not with any other units. And not necessarily the flight lead only.

Weather injectors like this one can set cloud heights to values we are unable to in the mission editor. It unpacks the .miz file and changles the height value in the code, so if you can find which line it is in the files you may be able to set them fairly low. https://github.com/evogelsa/dcs-real-weather/releases/tag/v2.0.0

This has been happening to me for as long as I can remember in the A-10, but I notice the wording is "may occur" in the manual while in the sim it will occur with 100% probability. Mine always disengages as I taxi clear of the runway on every flight.

Not for all of our modeled warbirds, unfortunately. Some of the other warbirds, notably the P-47, are modeled with a differing logic that causes damage or failure with any WEP usage--or even the slightest mistreatment--at all.

Still waiting for simple fixes like the screwed up rudder texture that's 1~2 years old by now.

Image of the geometric shenanigans when it crashes:

Ah thanks, was expecting it in the Mods folder.

The rings are very inconsistent. For some units the outer red ring is detection distance and the inner ring is firing range, but actual engagement range may be less than indicated. The only one that seems 100% consistent is the green min engagement distance ring.

There are various GoPro angles that don't require a visible head.

I've experienced the same, always when the temps are colder. If you connect and apply ground air before start up the fault doesn't occur.

Name has to match that of the "makeview" entry, which is also appears in snapviews lua file. The F-4 code won't work for the F-5E either because it has two viewpoints (pilot and WSO) and the camera location code is different. You have to copy the F-5E's code from it's view.lua, paste it into server.lua, and add the proper name in [""]. This is all explained in that tutorial and thread. F4 pilot is headless because only a couple of modules have the auto-pop-in head: Viper, Hornet, Apache, Chinook, and maybe the Hind.

Nice! I can get some good trap footage from the Airboss station now. I'm curious about this one. Vic is a 3-ship formation, so there should be no "No.4" at all. Is this a typo?

Didn't the B(U) upgrdade come with DFCS as well? I assume that would require some FM tweaking that would make this a bit more "in the future."

Main folder views.lua isn't the best way to do it. The best way should be to edit them in the Saved Games server.lua, as explained here: For the F-4 this is my entry: ViewSettings["F-4E-45MC"] = { Cockpit = { [1] = { CockpitLocalPoint = {5.10364, 0.77765, 0.0}, CameraViewAngleLimits = {20.000000,170.000000}, CameraAngleRestriction = {false,90.000000,0.400000}, CameraAngleLimits = {200,-90.000000,90.000000}, EyePoint = {0.00000,-0.0,0.000000}, ShoulderSize = 0.15, Allow360rotation = true, limits_6DOF = {x = {-0.9,0.9},y = {-0.9,.9},z = {-0.9,.9},roll = 90.000000}, }, [2] = { CockpitLocalPoint = {3.71, 1.07, 0.0}, CameraViewAngleLimits = { 30.0, 140.0 }, CameraAngleLimits = { 180, -80.0, 120.0 }, CameraAngleRestriction = {false, 90.0, 0.50}, EyePoint = { 0,0,0.000000 }, ShoulderSize = 0.15, Allow360rotation = true, limits_6DOF = { x = {-0.9, 0.9}, y = {-0.9, 0.9}, z = {-0.9, 0.9}, roll = 45.0 }, }, }, -- Cockpit Chase = { LocalPoint = {-5.0,1.0,3.0}, AnglesDefault = {0.000000,0.000000}, }, -- Chase Arcade = { LocalPoint = {-21.500000,5.618000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade }

My only disappointment is in teasing us with something that we may never even get.

F-4's works fine for me. As well as the F-14A/B, Viggen, and Apache.

I do a lot of filming and screenshot taking in DCS, and for a lot of cockpit stuff I need to loosen the 6DOF limits to get close-ups of the dashboard and GoPro style footage of the pilot body, which works for all the modules except the warbirds. Changing 6DOF limits in a server.lua file in Saved Games, as I do for all other modules, doesn't work. Changing 6DOF limits directly in the modules' view.lua also does not work. However, unlocking 360 rotation does work. For me, the current warbirds are affected: Fw 190 A-8: 6DOF not unlocked, 360 rotation unlocked Bf 109 K-4: 6DOF not unlocked, 360 rotation unlocked P-47 (all variants): 6DOF not unlocked, 360 rotation unlocked Spitfire (both variants): 6DOF not unlocked, 360 rotation unlocked Mosquito: 6DOF unlocked, 360 rotation locked The Mosquito is the one exception, where 6DOF edits work but the 360 rotation edit does not.