Ramsay

For me (9900K 8 core/16 thread) - Initially (my first 3 or 4 flights) the default 4 threads seemed ok - workflow: HRM at 30-10 NM --> freeze map/designate TGT --> run in, use TPOD to ID/sweeten target and drop LGB However I quickly found in both cold starts and air spawns 4 Threads = CTD, once I started using the HOTAS to take various sizes of HRM patch maps on the LMPD while also having the TPOD on the RMPD. 6 Threads - seemed to "fix" the CTD's ... but I've settled on 8 Threads on the basis it "might" give a little more headroom and it's 50% of my CPU's available threads. FPS is mostly unaffected (drops 1 fps) but a simple DCS Multi-thread training mission usually runs at +100FPS and I have Vsync set at 60 FPS. YMMV and I'm still testing.

AFAIK the in game pilot eye position is a compromise between the real life eye position and cockpit readability - which why there are Special Options VR and Monitor eyepoint offset adjustments in DCS>Options>Special>F-15E

They are NDB's (non-directional beacon's) used for navigation. https://en.wikipedia.org/wiki/Non-directional_beacon AQC @326 kHz is a real world beacon. https://skyvector.com/?ll=29.92351768255035,35.128440870413186&chart=301&zoom=1

It's a known bug - AFAIK it's already been fixed in PC's internal build and is waiting to be pushed out with ED's next patch cycle (likely sometime in July but who knows for sure). The cyclic has full movement in my install - so the limitation seems particular to your set up. I suggest checking you axis settings and that Y Saturation = 100% Note the old recommendation was to set pitch saturation between 40-60%, so if you're still using your old curves/saturations - you'll want to reset your joystick settings and fine tune from there.

Dumb bombs don't self identify - so the PACS page needs to be used to set the bomb type. Explained here @23:16

Yes, my secondary PC has a 1st gen i7-860 @2.8MHz - paired with a RTX 2070 Super it runs Multi-threaded DCS at 80-90 fps. Noting that a CPU supporting AVX is required to run the DCS F-15E in the specs. would seem sensible (unless the requirement is a compiler error).

AFAIK we will get mavericks later during early access as they were tested on the F-15E and pilots were trained to use them. Mavericks were never deployed operationally, so having them for the initial EA release was (understandably) a low priority compared to having a solid TGP/LGB implementation. Later in development the F-15E will get the AGM-130 which was used against bridges and SAM sites, however it was more a DEAD (Destruction of Enemy Air Defences) weapon than SEAD.

Not sure what you are doing wrong, as RAlt+Num0 will always save to the last used snap view ? Procedure is 1. Backup "Saved Games\DCS\Config\View\SnapViews.lua" so you can always revert if you mess something up. 2. Enter aircraft (disable TrackIR, etc. as req'ed) i.e. a cold start spawn 3. Check default snap view is selected i.e. Slew head position right with Num6, then tap Num5 to return to default/center view 4. Adjust FOV with Num/ and Num* and/or head position as req'ed (do not select another snap view until finished) 5. Once happy with the new default view, save it with RAlt+Num0 6. Exit the mission and confirm "Saved Games\DCS\Config\View\SnapViews.lua" has been updated i.e. has current date and time or the relevant P-51D section has updated. 7. Enter the aircraft a 2nd time and confirm the starting position/FOV has taken. 8. Repeat for other views/panels as desired. Tested DCS Open Beta Multi-thread 2.8.6.41066

AFAIK Auto hover, etc. for the new FM wasn't ready in time for ED's patching cycle - so doesn't work. Current recommendation is to use the regular cyclic trim and avoid auto-hover/slave.

7th September 2020 the AV-8B was said to be out of it's Early Access period and "feature complete" It's continued to be developed/improved with the addition of the Gen 4 Targeting Pod, APKWS, etc. and a still to come, INS rework.

AFAIK • Only basic Trim and SAS are working. • AFAIK SAS/damping works off your last trim position but is WIP due to the new flight model. • The old AP speed and altitude sub-modes, hover hold and auto-slew weren't ready in time for the current patch - so their use can be unpredictable. • Unfortunately rudder trimming is bugged (uses offset from center, rather than current position), so should be avoided if possible.

Is there any update on this, currently distance is the only value being displayed correctly when flying on the Caucasus map ? Distance 15.2 NM Ground Speed 64 KTS (correct value ~115 KTS) Ground Track 185°M (correct value 179°M, what is displayed is the TRUE) ETE 14:13 (incorrect due to wrong ground speed, should be approx. 7:56) Desired Track 195°M (correct value 189°M, what is displayed is the TRUE) Bearing to waypoint 194°M (correct value 188°M, what is displayed is the TRUE) DCS Open Beta Multi-thread 2.8.6.41066

Try the same in the "L" as it's lighter - I have no issue when starting with 66% (350 litre) of fuel. Note there is a known bug and using the rearm/refuel ground crew dialog doesn't change the aircraft's weight (fuel load needs to be set in the mission editor). A "standard" ALAT M1 loadout is 2 HOT Missiles with 66% (350 litre) fuel, however PC are checking the current equipment weight and aircraft performance with SME's i.e. the FM is still WIP and certain aspects may require further tuning AFAIK in a temperate climate, near sea level, with light winds - you should have no trouble flying with the new FM (the Gazelle is limited by it's Max allowable torque). Only at higher altitudes/ air temperatures will the engine limit max performance. Not sure as, it's not something I see - do you have any old settings, axis curves or a control conflict ?

AFAIK all the major FM features are in and adjusted to match the US Flight Test data. Possibly there's some fine tuning still required to match RL Gazelle M1 SME feedback (so consider the current FM still WIP) but overall I'm very happy with what Polychop have achieved.

The "L" is lighter than the "M", so I would start off testing that version (I've tested that on the 4YA Syria server near sea level). Unfortunately (fortunate for me) - most of my SA-342L test flights have been in single player where I've already set a 66% (350 litre) fuel load in the mission editor.

Perhaps you have, a video, track or at least screen shot of your input curves might help diagnose why you are having issues. LTE (loss of tail rotor effectiveness) is a real thing, where the tail rotor has insufficient authority to compensate for large amounts of torque, crosswind, etc. Again a video/screen shot of your settings, curves and control inputs (RCtrl+Enter) would help us, help you. Note there is a known bug ATM - if you spawn with a full fuel load - reducing the fuel load (via the rearm/refuel dialog) does NOT reduce the aircrafts simulated weight.

I reproduced this bug on the 4YA Syria server - not sure of the cause but it's reported.

TL;DR: Helicopter's don't trim like fixed wing aircraft and crab slightly in forward flight Detail: • centered ball = in aero-dynamic trim • centered yaw string / doppler needle = in nose to tail trim Being in nose to tail trim is useful as the nose (and hence gun, rockets, etc.) is facing the direction of flight. Aero-dynamic trim is the most efficient/least draggy and preferable most of the time. Casmo explains it well in this Apache video @21:34

Depends on personal preference and what you want to do with it. • Tablet gives you the correct GS (something that's been broken in the NS430 since Christmas) • OTOH the NS430 gives cross track error, ETE, etc. and has a Airport DB that gives Lat/Long that can be typed into the NADIR. The NS430 "should" be better than the NADIR if managing a flight plan with more than 9 waypoints (but ED have left the NS430 more or less unsupported), while the tablet is prettier. Pick up the Gazelle NS430 in a sale as a semi-functional cockpit decoration/instrument - but that's just me and YMMV.

Note: Spawning in the A-10A slot before switching to the SA-342L was good, only crashed when I switched back from the SA-342L to the A-10A (I haven't tested all the other possible combinations - main purpose was to see if I could generate the reported crash).

Reproduced a crash on the 4YA Syria Server 1. Load into SA-342L at FARP-London, Load up 4 HOT Missiles and Sand Filter, take-off/hover taxi and land 2. Select Spectator Role and check map 3. Select A-10A slot at Incirlik - DCS Crashes to desktop/triggers crash reporter 4. Steam validated all 100482 files (548.7 GB) as correct. dcs.log-20230612-204554.zip

Yes, it's a limitation of DCS (grass has no collision model). AFAIK choices are 1. Don't land where there is tall grass 2. Remove the grass using a Mission Editor zone 3. Reduce/remove the grass in settings to your own personal preference

The tablet uses GPS, so is only available in missions dated after march 1994

Where do you get this information ? AFAIK the control positions have been tuned using SME feedback and US Flight Test Data which show the cyclic aft and slightly left of center (50%) in a hover (0 knots) in both IGE (3-5 ft) and OGE (75-100 ft)

You may be better off reporting NS430 bugs in the "DCS: Tech & Terrain>DCS: NS430" sub-forum as the NS430 module is developed by Eagle Dynamics https://forum.dcs.world/forum/306-bugs-and-problems/ ED's moderators can then add your report to their internal bug tracker or ask for further details as req'ed. (note the NS430 seems low down on ED's priority list, so I wouldn't expect a quick fix).