Fresh

Hi all, the VNAO's T-45C engine will windmill at 1% RPM with wind above 15 knots. Does anyone know how to edit the windmilling behaviour of a jet engine that is shutdown correctly (or not even started up)? Thanks in advance, Fresh

Press the D/L button twice and check at each press you see it "ON".. there are sort of like two pages in the D/L button..

Hi Elphaba, the code I posted was code I used in an aircraft mod (VNAO T-45C), in the cockpit/scripts folder. I didn't realise the OP was referring to missions scripts. Sorry for getting your hopes up. Are you trying to make the ship turn into wind? Have you tried the AirBoss Moose script? Fresh

The first 5 missions in the .lua are commented out by the developers. By "commented out", I mean there are two dashes, which means .lua ignores it, as if it is just comments in the code for the programmers. So at some point they removed those missions.

Hi pcartier, the SC chooses what case is active depending on the weather and sun. If you want to learn to land I suggest Bankler's mission: Use normal Comms (I don't know about simplified comms), make sure you are on the correct frequency (in Bankler's it is on button/channel 2). Get into the comms menu, Alt-\ (or whatever you bound already), then press "ATC", then the ship, then "Inbound". In the control settings you can bind a hotas/joystick button to the "Hornet Ball" call. The picture you show, is what you see when Case II or Case III is active, and you already checked in inbound. If you have discord (highly recommended) join the DCS discord server, you can stream your screen and me or someone else can point you in the right direction. Have fun' Fresh

Hi All, here an update to icons used in DCS for the Goshawk. Adds 76x76 icon for training and missions folder.. Adds icons for the main screen buttons (bottom row icons). Enjoy! Fresh Put the three .png files in the Theme folder, where you can see the original icon.png file. Theme.zip

Ah, those two missions only become visible if you select "Instant Action".. I'm working of making something for the "Training" and "Mission" section.. (Yes, with Rudel's missions). Fresh

Hi Tonker, where is that .lua file you are referring to? Fresh

Bankler's works fine, the new FM is just a little different and takes getting used to.. my average went down by about 10 points [emoji6]

I haven't had any issues with the Mediafire, and you can run a virus scan on it after downloading...

Try my bombing mission: https://www.digitalcombatsimulator.com/en/files/3319779/

Hi Bankler, sorry my bad, I didn't disable the supecarrier module when I wanted to test the legacy version, and since I was trying to use the T-45C I had mistakenly used the supercarrier version on top of that.. Sorry for the trouble.. Fresh

By Michael Puoci: VNAO_T45_smoke_ON_V1.0.1.zip

Glad that worked! ;-)

If you have the time and energy try a fresh install of the T-45C. I did a fresh install myself and then added the zipped Scripts folder to test before going public. Sent from my iPhone using Tapatalk

Hi Deep, strange... is anyone else experiencing this? If you select to have the HUD repeated in one of the MFDs are you seeing the same thing? There have been Font issues in the past. Have you installed any other mods? Thx, Fresh Sent from my iPhone using Tapatalk

Hello Naval Aviators, I've been working on updating some of the scripts in the Goshawk, fixing various stuff: 1. Magnetic variation from the map implemented, TACAN, VOR and Waypoints magnetic bearings now correct. 2. Switches for the radios now work in the correct direction. 3. 264 MHz and 305 MHz are automatically set on the radios (Bankler's Case I training mission, to talk with buddies via SRS). 4. COMM1 and COMM2 are automatically audible and on when you have a hot air or ground start. 5. Parking brakes are set on ground by default. 6. ADI is on MFDL and HSI is on MFDR by default on a hot start. 7. Antiskid is on by default for a hot start. 8. ILS is on and tuned to 110.30 Batumi ILS. 9. TACAN is on and tuned to 72X. 10. Data Page on either MFD is cleaned up and shows magnetic variation and QFF from the map. 11. Hides the NATOPS Kneeboard CHL. 12. CDI for TACAN and VOR now show correctly when using the reciprocal course. 13. Altimeter starts at the correct setting, within the limits of the Kollsman window. 14. Wind displayed on the HSI is now in the correct direction (was 180° off) 15. Added a temperature error to the altitude based on QFF and sea level temperature All these changes are in the Scripts folder which I have attached below. Please read the readme.txt file to know where to install (replace the original). Feedback and info about any new bugs introduced by my tinkering very welcome. Fresh 2024-FEB-18 Scripts Update.zip

Hi Slippa, if you didn't know, there is smoke pod script for the Goshawk. Check out VNAO's Discord. Brgds, Fresh Sent from my iPhone using Tapatalk

Hi Vakarian, your test is difficult to interpret without knowing where you are. I suspect from the temperature range you are in the Mariannas, maybe Andersen based on the QFE? (Sorry, using my iPhone, can't watch your tracks). Try January in Beslan, Caucasus with -12°C and same place in July with 50°C. Beslan being high will show bigger differences. If you have Nevada, try Tonopah (5540 AMSL) So your test tell us how the different developers coded their altimeters. As the OP says, each developer used a different formula to create the temperature error if at all. If you do try Beslan or Tonopah maybe do one test with 15° C (Standard ISA Temp) Another test is to turn the altimeter from 28.00 to 29.00 and 29.00 to 30.00 to see how many feet an inch of mercury changes. From my research it should be 938 feet. The change is not linear, but I suspect some have used 1000' per inch. That will influence when 0 feet is reached as displayed on the Kollsmann window. Thanks for your efforts! Fresh Sent from my iPhone using Tapatalk

QFF, QNH, QFE concepts and temperature and density effects in the atmosphere are quite complicated subjects, let alone the calculations for them. It would be great if there was some guidance material from ED on best practice for 3rd party and mod developers so that we all get standardised results for indicated altitude and indicated airspeeds. Perhaps a funtion to give indicated altitude and speed instead of the current true altitude. Ideally AI would also fly at such indicated altitudes, instead of true altitude. It would be great to set up a tanker in the mission editor to fly at a flight level, and pilots could join at the same flight level. Anyway, just my thoughts, getting off topic from OP...

Thanks Silverdevil, I was hoping those 3rd party programmers could share their knowledge and help me fix this. Or maybe the community could lay down a code for all mod creators, so that all our altimeters and indicated speeds are more or less correct (not counting specific airframe differences). Fresh

Hi everyone, I am trying to get the T-45C Goshawk mod to have the same indicated altitude as the Hornet. I've created a mission in Nevada, set QFF to 29.92 and the temperature to +50°C I then place a Hornet, a Tomcat and the Goshawk above Tonopah at 35,000 feet in the mission editor. The Hornet reads 31280 feet on the HUD The Hornet reads 31060 feet on the altimeter The Tomcat reads 31195 feet on the altimeter These readouts stay the same at Mach 0.5 and Mach 0.8 My code for the Goshawk makes it read 30740 feet on all three outputs (same code for each) local alt = ((sensor_data.getBarometricAltitude()*meters_to_feet)-(qff_inHg:get() - ALT_PRESSURE_STD)*938) local temp_error = ((temp - 15)/((273.15 + temp)-(0.5*0.00198*alt)))*alt --add an error for temperature effects on the atmosphere alt = alt - temp_error --add error to altimeter indication Can anyone look at my code and see if there is an error. I guess the Hornet and Tomcat programmers did not include altimeter system errors for Mach, but I will test further... (Hornet performance info says a/c is ca. 300 feet higher at M 0.8 than indicated on the altimeter and that FCC corrects it otherwise, I guess on the HUD) Much appreciated! Fresh

I suspect CSS is another one of those lesser understood features of the Hornet.. Try this: 1. Fly straight and level, press the A/P button and then press and hold the ON/OFF button. (Make sure you have not selected any modes, you are now is "control stick steering" mode (CSS)). 2. Note the "ADV-A/P" advisory on the left DDI. Feel how the airplane responds. Note how much stick displacement you can make before the AP fails, also experiment with pitch and bank limits (gently).. Master caution light comes on and "AUTO PILOT" displayed when the A/P fails. 3. Use the paddle switch to exit all AP modes. (Default "A" keyboard button). 4. Fly straight and level again, without any stick input/pressure. Press A/P and then press BALT mode. You will see the mode displayed in the left DDI "ADV-BALT". If you now use your stick gently in pitch the BALT mode will fail, but because it was gentle, the A/P reverts to CSS mode. If you had been rough CSS would also have failed, and you would be without A/P. Monitor your A/P mode with your DDI advisory. Vertical modes (BALT/RALT) will let you change bank, lateral modes (CPL/HSEL) will let you change pitch. 5. Do 4. again, when you are in BALT mode, just press BALT button again.. note you have defaulted to CSS mode with "A/P" as well. Certain failures will give you such mode reversion, e.g. switching off your radar altimeter when in RALT mode, or switching TACAN frequency when CPLD. Note: if you have a lateral AND a vertical mode active, and one of those modes fail, you will get the "AUTO PILOT" master caution, but you will still be in the unfailed mode. eg. you are in BALT/HSEL mode and change pitch, then you will be in HSEL mode laterally, and free vertically. Have fun experimenting! Fresh

Hi Ivo, Wags does say at 0:27 that there is another video about case 3 recoveries.. and it is linked in the comment section. Here is a link to Wags video on how to set up the carrier: Please save and send us your replay file of your failed attempts. (it has a .trk file extension).

Hmm, try to make sure you are trimmed out and not making any stick inputs. Maybe make your deadzone a little bigger for test purposes.