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.

Hi, the supercarrier needs you to trigger certain events, you need to call mother, then go through all the comms, then check in to tower and call platform etc.. otherwise things will not work. Also the boat has to be in Case III mode, so you need to be after sunset +30'/before sunrise-30' (I haven't tested exactly when it changes to Case III) or have ceilings/vis below Case 2 (also I don't know exactly when the supercarrier changes case based on weather)... This Case III approach is similar to an ILS in IFR operations. If you don't know anything about IFR flying, like holding patterns, radials etc. it might be quite difficult.. Have fun!

Hi Ivo, Case I is used during day with good weather. The pilots use the IFOLS light for the last 17 or so seconds in final ("the groove"). Case III is a night time or bad weather ops. The recovery rate is then lower. Maybe explain why you want to do ACLS during Case I so we can help solve the problem/issue.

At what time are you having an issue in the track?

I don't know if it helps, but you can get the magnetic variation (some contries call this declination) for an aircraft (mod) using true heading minus magnetic heading. local true_hdg = (360-(sensor_data.getHeading()*degrees_per_radian)) -- true heading local mag_hdg = (sensor_data.getMagneticHeading()*degrees_per_radian) -- magnetic heading local mvar = true_hdg - mag_hdg current_hdg:set(mag_hdg) -- magnetic heading current_mvar:set(mvar) -- magnetic Variation

Does anyone know how to find out the current QNH when in game, so that I can set the altimeter Kollsman window to it in a mod at post_init phase?

Just a heads up, in VR, the helpers are yet again different and partially "underground" in the panels..

That pitch up as you reach the boat is for sure wake turbulence. Disable "Wake turbulence" and enable "No force from mission, use mine" and see if the problem is solved. Be aware that forcing your own options may break whatever the mission designer had in mind...

When checking the bearing from bullseye I noticed that it goes from 359 to 360 to 000 and so forth.. so there are 361 degrees in a full circle? I expect the measurment to go from 359.9 to 0.0 degrees, at the moment it goes to 360.9, and then to 0.0 degrees as it were.. See attached images.

Hi ram0506, you should install the mod in your Saved Games folder: C:\Users\your..username\Saved Games\DCS.openbeta\Mods\Aircraft Don't forget to read the readme file ;-) Also go to the first page of this thread, there is a link to version 1.0.1 on a mediafire website from MadMaxter

I found a bug in the TACAN, and it is probably also in the VOR and WYPT implementation. Basically it receives the bearing in true, but displays it in magnetic. I am still trying to find out how to get the magnetic variation off the map, but a temporary workaround is to edit the Cockpit\Scripts\Nav\TACAN.lua file... in line 161 add a correction for the variation, like this: tacanBearing:set((math.deg(math.atan2((atcn.position.z-curz),(atcn.position.x-curx)))-13) %360) --temporarily added "-13" to correct for magvar in Nevada Add a parenthesis "(" before "math.deg" and add "-13)" before " %360)" I also found that in CDI mode it doesn't center the CDI if you have the reciprocal course. So it centers with a TO indication, but never when you have a FROM indication... I've attached 4 images. The first showing the Goshawk in the same position as the Hornet, notice how the Goshawk thinks it has QDM 041 vs the Hornet showing QDM 029. After making the edit above you see it now shows more or less correctly.. The last image shows the recipocal CRS set on the HSI, and the CDI stays full scale, instead of being centered. If you are not flying in Nevada use a different correction Does anyone have time to help me implement this? : local magvar = require("magvar") magvar.init(month, year) magvar.get_mag_decl(lat, lon)

Sure ask here! No problem! [emoji6] Sent from my iPhone using Tapatalk

It looks like you are landing short you seem to be pitching up like to flare.. don't, just fly that jet into the deck, on speed!

There is a single player mission for the F/A-18C called "Mission Practice - Air to Air Radar" Put yourself in active pause (LShift + LWin + Pause) right from the start. Then select AMRAAM weapon (LShift + D).. and then put it in RWS with 6 bar scan (equals about 20º vertical scan) and the full 140º azimuth. Increase the aging to 32 seconds (Data sub page). Press sensor select left (RAlt + ,) to show the AZ/EL page. Then sit and watch the bricks.. on the left DDI you will see the track files. You can adjust the radar elevation (- or =). Change the elevation scale to suit the situation. Use the F10 map to see what you are missing and then see if you can find them. Depending on the target aspect and range and interleave you will see or lose targets... Hope that helps for a start..

Hi Bankler, I've installed your latest legacy version, and noticed it is not legacy anymore. I don't know if I am doing anything wrong. Anyway, I changed it to the Forrestal, and now I broke it Can you please have a look at it? Thanks!

Hi guys I was flying against a Su-30 mod (AI) and I suddenly exploded. Is there a known bug of invisible rockets? In the replay and in Tacview I could not see the Su launch anything.. very confused! Thanks for a reply if anyone also experienced this!

Dispense FWD for Mode 5 Dispense AFT for Mode 1 (or whatever is displayed) https://chucksguides.com/aircraft/dcs/fa-18c/#pf262 Part 11 has the description.

do you have wind in your mission? If yes, try a run in from the opposite direction and see if the result changes much..

I suggest you use Bankler's trainer, put it in pattern mode and leave the hook up and practice, practice and practice... use Tacview to analyse your pattern. The runway markings are harder to see than in real life so you have to use the wake as a reference until you can see your lineup. The speed and bank angle for your turn to downwind will determine your abeam distance, so that is where you have to get it right first, not the last part.. set up your HSI so you can see the course line and the distance off the line, rather than the distance from mother.. try for 1.3-1.4 Good luck, you can DM me if you want me to help you more.

Thanks razo+r for your reply, that makes sense. I guess, personally, I would prefer it to just go black, then in VR I wouldn't see a source of light there.. but the workaround is easy enough, just toggle the mirrors. But it is ever so slightly immersion breaking..

If you look at the picture, you can see that I am in the F/A-18C. We took off at sunset and I folded the mirrors then. Later on, I noticed in VR, that I could still see the day version in the folded up mirrors. I cycled the mirrors and the view changed to night. Tested this again morning with the track replay and the issue is also in 2D. I'll create a small .miz and upload a .trk later on. Digital Combat Simulator 2023-12-06 11-21-23.mp4 Mirror.trk

Here's a second track, this time with my mods uninstalled except SRS and Tacview. Same result.. ATC Bug Nov #2. 2023.trk