Nealius

I'm refering to the aeronatical chart on the mission editor/planner/F10 map.

I'm quite confused by the airfield/heliport choices: 1. There's a truckload of gliderports that serve no purpose unless we're getting gliders or Piper Cub modules. 2. Most of the heliports (non medical) on the FRG side are located where no such indication of a heliport or airfield existing is on the aeronautical chart. 3. A few military fields are depicted as civil glider ports: E.g. Waren should have been a forward base for Hinds.

In the mission editor it's really hard to quickly identify and locate fixed-wing airfields due to the clutter of heliports/helipads. In the mission editor's map options menu (key icon) it would be nice if "heliports" could be added to the filter.

Awesome thanks!

Nice skins on the Brit kit! I have to wonder though, what was ED’s source material for these because there are a lot of inaccuracies on the modeling for both Yanks and Tommies (wrong bayonet, Bren pouches sit too low, P37 straps too long, rolled blanket instead of gas mask pouch, etc.).

Same issue with Quest 2. If I take the rifle off the dash with hand controls, I don't get doubled guns, but it's impossible to place the rifle back in its cradle. It gets frozen in mid-air.

Stable hover, with some wind (3-6kts), is achievable if you get into a stable hover first, engage ATT hold then ALT hold in that order. I used to say "eh close enough" and hit the ALT hold and things were steady, but now doing so will take you on an unwanted rollercoaster ride (usually forward and left for me). In forward flight the hold modes are useless. The nose constantly yaws right or left and refuses to maintain a heading track. They used to be steady. And of course the finnicky yaw, and an extreme sensitivity to tail winds causing LTE situations. The "WIP" tag on this thread doesn't make sense when the "WIP" FM was in a much better state in the previous update. This is an accidental regression to a previous FM build.

Would rather get more relevant liveries like hi-vis Dbacks F-14Bs and '80s~'90s Swordsmen F-14As rather than worry about how far a single red stripe extends on one of the sixteen variations of Jolly Rogers we have.

Is the Kiowa not supported? I can't find it in the aircraft list when I open the debrief file.

To Avio's point, I also haven't noticed such a pitching behavior in any of the other modules, including the props and analog jets. Nor did that other sim that offers a realistic recreation of the Viper's FLCS have it.

I'm hoping with the DTC we can load pre-made CMDS and MFD setups instead of having to manually set them through the DTC UI each and every time we hop into a mission and server.

It says "dcs_server.release." No idea what my older version had since I uninstalled it.

If I'm flying around a particular area and want a specific temp I adjust by the general 2C per 1000ft rule. So If I want 30C at Bagram I input 39 or 40 into the system. It does get irritating though when the map's temperature settings don't have a realistic range.

And it's gotten a lot better since the flight model tuning a few months--maybe a year? ago now. It used to overshoot its 1G trim and continue creeping at 1G, and rolling out in level turns required a healthy dose of forward stick. Now it doesn't creep as much nor does it need forward stick, and I honestly don't find it significantly different to handle than any of the other modules, FBW or analog.

A complete uninstall and reinstall fixed it. Did the moduler server get an update? The old one was "DCS.openbeta_server" but now it's "DCS.dcs_serverrelease," and it creates a second folder "DCS.release_server" with two config files that aren't even used.

You also have the Q-direct option where your headmovement can slew the TGP on the VDI repeater.

ED (I can't remember who; either Bignewy or one of the beta testers) specifically instructed us to use the laser for improved JDAM accuracy.

Is our avionics tape supposed to have 80nm selectable at all in GMT? Documents for an older Block 50/52 lists max display range 40, and specifically says that 80, DBS1, and DBS2 are not available in GMT. I haven't experienced this instantanous finding of targets in the F-16. It is fast, yes, but it still takes a complete radar sweep before a blip appears. However it's much easier than working with the Mudhen's radar, as the Mudhen requires some fidding with the antenna elevation to select the band of ground you want to search. The Viper casts a very wide net that reduces pilot workload. No idea if or how realistic that is.

I thought fan breaks were a Navy thing. I'll have to look into that.

No change when disabling launcher in options.lua. I don't know what "settings.json" and "launcher.lua" are. Those aren't in my client install either.

I don't know if this is related, but the server won't run from the bin/DCS.exe. It will only run from a desktop shortcut, but the shortcut directs to the same DCS.exe so it makes no since for the DCS.exe to not run when bypassing the shortcut. 2025-04-06 10:07:30.582 ERROR EDCORE (Main): No suitable driver found to mount launcher 2025-04-06 10:07:30.587 ERROR EDCORE (Main): Can't open file: /settings.json. 2025-04-06 10:07:30.587 ERROR EDCORE (Main): Can't open file: /launcher.lua. 2025-04-06 10:07:30.604 INFO EDCORE (Main): try to write dump information 2025-04-06 10:07:30.617 INFO EDCORE (Main): # -------------- 20250406-100731 -------------- 2025-04-06 10:07:30.619 INFO EDCORE (Main): DCS/2.9.14.8394 (x86_64; MT; Windows NT 10.0.19045) 2025-04-06 10:07:30.621 INFO EDCORE (Main): F:\DCS World OpenBeta Server\bin\DCS.exe 2025-04-06 10:07:30.623 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff674482b99 00:00000000 2025-04-06 10:07:30.625 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'F:\DCS World OpenBeta Server\bin;', symOptions: 532, UserName: 'neali' 2025-04-06 10:07:30.627 INFO EDCORE (Main): OS-Version: 10.0.19045 () 0x300-0x1 2025-04-06 10:07:30.628 INFO EDCORE (Main): 0x0000000000a92b99 (DCS): SW + 0x47C879 2025-04-06 10:07:30.630 INFO EDCORE (Main): 0x0000000000a7b064 (DCS): SW + 0x464D44 2025-04-06 10:07:30.632 INFO EDCORE (Main): 0x0000000000a78c16 (DCS): SW + 0x4628F6 2025-04-06 10:07:30.634 INFO EDCORE (Main): 0x0000000002621777 (DCS): AmdPowerXpressRequestHighPerformance + 0x1142773 2025-04-06 10:07:30.636 INFO EDCORE (Main): 0x000000000261c710 (DCS): AmdPowerXpressRequestHighPerformance + 0x113D70C 2025-04-06 10:07:30.638 INFO EDCORE (Main): 0x00000000010a64ce (DCS): SW + 0xA901AE 2025-04-06 10:07:30.638 INFO EDCORE (Main): 0x0000000000017374 (KERNEL32): BaseThreadInitThunk + 0x14 2025-04-06 10:07:30.699 INFO EDCORE (Main): Minidump created.

The few free documents on there were interesting, particularly the descent down to a perpendicular break. I rewatched Mover's demo in the Viper on the Iraq map, which is just a standard tactical overhead at higher altitude and speed: 4,000ft AGL 400kts. This is what I've been doing in the Viper and Mudhen, but I need to tighten up my pattern a bit. I always end up with a 0.5-1.0nm final. Still, all of these are singletons. I'm wondering how they deal with 2-, 3-, or 4-ship flights.

Windows default AV is disabled except for quick scans. Not running any 3rd party AV at all. I have confirmed this is an issue with the 8394 update. When I roll back to 8222 it works fine. @NineLine @BIGNEWY @Flappie are there no bug reports open on terrains being disabled on 8394 dedicated servers? (I didn't reinstall Sinai, just Afghanistan and Kola) dcs-2.9.14.8222.log dcs-2.9.14.8394.log

Using DCS_updater.exe command to uninstall the terrains and reinstall them does not resolve. Terrains are still "unauthorized" on the dedicated server install.