AndyJWest

Opinions seem to differ on this. It has been suggested that since the ball is configured for the Hornet, following it precisely may not put you in the optimum spot. And there may possibly also be some subtle errors with the hook positioning and/or landing gear position and behaviour that affect trapping negatively. Some people seem to follow procedure and trap consistently. Others do the same thing, and have issues. Personally, I've not been able to be consistent enough to say one way or another, though it is clearly better for my ego to say it's the sims fault not mine. I'd concentrate on trying to be consistent, and if you can do that, maybe try experimenting a bit to see if you can 'tweak' your approach slightly from the 'exact' real-world optimum to get better results. The mod is a work in progress, and it is possible that any issues will be resolved in a later release.

Have you tried restarting Windows, rather than shutting it down and turning it back on? Win 10 behaves differently by default than previous versions, and during a normal shutdown will 'hibernate' the kernel to storage, for faster startup. A restart will sometimes fix odd issues that shutting down won't, since it gets things going again from scratch.

See the v1.0.1 changelog: "Removed SRS script from download; the T-45 is now integrated into the latest SRS update".

My beta install is 267.4 GB. 169.5 GB of that is in the 'terrains' folder. The maps use a lot of storage.

You use AoA, not speed. Much more precise, in an aircraft that can vary quite a bit in landing weight. And note that you don't flare for landing. I think there may be a bit of an issue with trapping currently though, as the mod aircraft sits too high with weight on wheels. This might possibly hold the hook up a few inches higher than it would be IRL.

Won't that give you a negative result if the wind 'direction to' is less than 180 degrees? I've not tried it, but I think this should probably give the right result, if I understand correctly how Lua math.atan2 works: local windDir = math.deg(math.atan2(-WIND_Y:get(),-WIND_X:get())) Note the minus signs.

Why are you expecting a different response to the last time you made this request, three weeks ago? https://forums.eagle.ru/topic/269391-will-pay-to-fix-mig-31-mod/?tab=comments#comment-4645001

You need to be at 20,500 lbs or less for VTOL, per Chuck's guide.

What weight are you trying to take off at?

The mod is built for 2.7. It won't run with earlier versions.

I think I've confirmed that the error on the HSI is due to not taking magnetic declination into account. Use the editor to set up a T-45 on the Nellis AFB runway, with the next waypoint aligned with it, to the northeast. The HUD etc show the runway heading as about 28° (the runway is marked as 03, as rounded per standard practice), but the heading to the waypoint is shown on the HSI as something like 40°. If you take off straight ahead, and maintain you heading as shown on the HUD (28°) you will overfly the waypoint. Magnetic declination in Nevada is about 12° East.

Is this an issue with the difference between true north and magnetic north not being taken into account on the HSI?

Many thanks, Chuck.

Yup, it's a three-way switch. Incidentally, you'll be better off asking for help in the T-45 thread, rather than in the general DCS world subforum, if you have problems with the mod. People with relevant knowledge may not see it here. https://forums.eagle.ru/topic/203816-vnao-t-45-goshawk/#comments

Small bug, I think. The wind direction as shown in the HSI using the DCS mission builder convention - the direction it is blowing to - rather than the standard for meteorology and aviation (e.g. METARS, ATIS etc) which is to report the direction the wind is coming from. It is possible the Goshawk reports it like that, but it seems unlikely.

Make sure you have moved the master engine switch back to 'on' from 'start' once the engine is running.

If you know the mod isn't built for the version you are running, making posts about things not working isn't helping anyone.

The mod is built for 2.7.

It isn't a toggle, you need to hold it down - there is a green indicator light for this on the warning/caution/advisory lights panel.

According to NATOPS, the T-45 is pressurised to a maximum differential of 4 psi. Which means that at the 40,000 ft ceiling you will need supplementary oxygen to keep the oxygen partial pressure up to safe levels, if I understand this correctly. The on-board oxygen generator system (OBOGS) provides this. From a brief search, it looks like the Hawk also had a maximum cabin pressure differential of 4 psi: see here, p. 37. https://www.aerosociety.com/media/4842/the-hawk-story.pdf

Excellent!

Answered earlier in the thread: https://forums.eagle.ru/topic/203816-vnao-t-45-goshawk/?do=findComment&comment=4641599

Regarding pressurisation, I found a T-45C bingo reference table online, which gives the altitude for the longest-range (250 nm) bingo fuel calculation (gear up, flaps up, drag index=0) as 40,000 ft. I'd assume that a long-range cruise is the only time you are likely to benefit from operating that high. A word of caution though. The VNAO Quick Start Manual says that the OBOG (on-board oxygen generator system) is 'not simulated'. Oxygen deprivation at altitude does however seem to be - or at least, after flying at 35,000 ft and 220 KIAS for twenty-odd minutes, checking fuel consumption, I got DCS's simulation of hypoxia - blurred image, and the onset of greying out. Whether it does this consistently, and under what conditions, I don't know. Not a criticism (this is a free mod, and a WIP) but something you may need to be looking out for if you are up high for extended periods, and don't want to have to do a simulated emergency descent.

I've had mixed results recording tracks. Sometimes they will play back fine, often they won't. Given the general problems DCS has with tracks, and the fact that this is the initial release of a free mod, I'm not particularly surprised at this.

I find having to hold a switch on while I'm looking around the cockpit with TrackIR rather awkward.