Nealius

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.

This is my fear, because it's not just the Mudhen but the Harrier, Mirage, MiG-19, South Atlantic, LHA, and South Atlantic Assets pack that all get impacted by this.

After the recent updates and moving my Dedicated Server install to a different SSD because of storage space issues, three of my maps are now not authorized on the dedicated server: -Afghanistan -Sinai -Kola These were working fine prior to the update, and they are still installed in the server's Terrain file structure. DCS repair does not resolve the issue. Terrains work fine on my main client install. No antivirus issues. No symbolic links or anything on the server except for liveries. dcs.log

If it were an issue of non-payment for services this issue would have been legally resolved by now. RB is not telling us what the real issue is.

It should be noted there are two different types of pitch-up movements being discussed here. The first, and the main point of my discussion, is the aircraft refusing to update stick position after releasing CD REL, causing the aircraft to violently pitch up because there's still aft stick input when there shouldn't be. In other words, the rotors are pitching. The second, which others have been commenting on, is when the stick position is updated after releasing CD REL, but the aircraft attitude gently pitches up causing a climb. In other words, the rotors are not pitching, the aircraft body is pitching via the LCT/DASH magic and causing an ascent. I've attributed the second issue to WIP LCT/DASH etc. dynamics. The first, and primary issue, however, seems to be more of a bug.

I've seen this happen in most, if not all ED modules. The Warthog's and Apache's CDU does the same thing. I believe I've also seen it happen with GPS coordinates, not just with UTM.

Helo landing spots are on the port side of CVNs as well. I believe there's one somewhere between cats 1 and 2, but most are on the port side along the angled deck. They're shaped somewhat like a T with a number. IIRC LSO does not direct helos, the airboss does. They pass astern, fly up the port side to their assigned parking spot, match speed with the moving carrier, then slide over and land so that the horizontal part of the T marking is passing under the pilot's butt. It's been a while since I read and tried the procedure but it more-or-less flows like that.

Nearly forgot the Viper's AG radar even existed. The thing is usually absolutely usless with its sh*t resolution for ground mapping. Finding movers with GMT is all I really use it for. Of course FCR/HSD methods only work if your brain can interpret where the bullseye coord is in relation to your current bullseye. Otherwise it's throwing punches in the dark.

In advanced waypoint actions, add "disperse under fire," then double-click it for additional properties. There's options for disperse radius and length of time they spend dispersed before continuing. Correction, there's just an option for length of time they're dispersed in seconds. Default is 600 seconds. I've set mine to 5 but haven't tested. Since disperse=off isn't respected there's a possibility the dispersion time may not be respected either.

Since the crew visor animations are broken we have to set the visors closed via the liveries' description.lua. Argument 1052 and 1053 are for pilot and WSO visors, respectively. Values of 0.0 and 1.0 toggle visor up or visor down, respectively. For visor down append this code to the description.lua for all liveries you want to have visors down: [1052] = 1.0, [1053] = 1.0, You'll have to redo it after every DCS update or repair. It also only works for external views. I'll do some digging to see if I can find a way to get the F1 view visors down. EDIT: Can't find the .edm for the F1 view pilot models. The cockpit.edm doesn't have them. The four pilot models in CoreMods are for after ejection, both pre- and post man-seat separation, but they don't have visor arguments that I can find.

Release physics are a bit bugged. Even with 2x GBU-12 on a CFT the bomb can be seen clipping through the fuselage as it releases laterally instead of straight down. Probably affected by winds aloft. Loaded on the forward CFT stations it doesn't cause damage, but you can see the odd release behavior.