AstonMartinDBS

Hier meine Checkliste für den Kaltstart der F-16C Viper für blutige Anfänger (wie mich selbst). Im Prinzip ist es eine möglichst genaue Verschriftlichung der folgenden Tutorials von Wags: DCS: F-16C Viper - Startup Procedure, DCS: F-16C - INS NORM Alignment Update (bis v1.3.0) und DCS: F-16C Viper - Stored Heading INS Alignment Tutorial (ab v1.5.0) In meiner Signatur findet ihr die Links zu meinen anderen Checklisten. Etwaige Fehler oder fehlende Schritte könnt ihr mir gern melden. Legende: Spalte 2 LK - Linke Konsole LHK - Linke Hilfskonsole IB - Instrumentenbrett ICP - Integrated Control Panel RHK - Rechte Hilfskonsole RK - Rechte Konsole HTS - HOTAS PDL - Pedale Spalte 3 Panel Spalte 4 SW - Switch/Schalter BTN - Button/Taste Spalte 5 R - Rechtsklick L - Linksklick W - Mausrad Verlauf: 02.04.2020: v1.0.0 (Veröffentlichung der Erstversion) 03.04.2020: v1.1.0 (mehrere unnötige Schritte entfernt, die einzelnen Punkte für das Panel AVIONICS POWER eingefügt und einige Kleinigkeiten optimiert) 04.04.2020: v1.2.0 (Prozedur für den Engine Start Request beim ATC hinzugefügt; Schriftgröße leicht verringert) 10.04.2020: v1.3.0 (INS NORM Alignment, CMDS, IFF und ein paar weitere Kleinigkeiten hinzugefügt; Schriftgröße wieder leicht erhöht) 06.04.2021: v1.5.0 (INS STOR HDG Alignment, einige Testroutinen entfernt, um die Checkliste auf eine Seite zu reduzieren, v1.3.0 steht weiterhin zum Download bereit) 30.01.2022: v1.6.0 (Check für Triebwerksstart hinzugefügt, HMCS hinzugefügt - Tutorial zum HMCS-Alignment sh. https://youtu.be/6qmf7dwF0ZQ?t=127, eine weitere Testroutine entfernt, um eine zweite Seite zu vermeiden, v1.3.0 und 1.5.0 stehen weiterhin zum Download bereit) Download: v1.3.0: DCS-F-16C-ColdStartChecklist-de-v130-A4Q1S.pdf v1.5.0: DCS-F-16C-ColdStartChecklist-de-v150-A4Q1S.pdf v1.6.0: DCS-F-16C-ColdStartChecklist-de-v160-A4Q1S.pdf Weitere Downloads: F-16C: ALIC Tables for the AGM-88C HARM (.pdf and Kneeboard) F/A-18C: Threat Codes for the AGM-88C HARM (.pdf and Kneeboard)

Same in 2.5.6.45915... when can we expect to get that simple menu items (in the comm menu) back? :music_whistling:

That workaround helps indeed. But I guess this is an incorrect behaviour. Here is another related thread: https://forums.eagle.ru/showthread.php?t=267874

Don't know, but I was able to reproduce that behavior twice when I've set only one station into the TOO mode (see attached trackfiles). After releasing the bomb the station is switching automatically to the next one, which is (still) in PP mode. I think that condition causes the TPOD to go into boresight mode. But when I set all stations to TOO mode before dropping the first bomb the TPOD doesn't go into boresight after the first release. In that case the automatic step to the next station after bomb release doesn't cause a switch to PP mode and the TPOD keeps looking to the targetzone. For that reason I guess, that the described behaviour is related to this bug-report: https://forums.eagle.ru/showthread.php?t=266782

Yeah, just hover the cursor over the comm dial knob and rotate the mouse wheel without pressing any other mouse buttons ;)

Check the mouses ettings in your windows control panel. Maybe reducing the scroll speed of your mouse wheel helps. Changing the channels in the F/A-18C works fine for me with the default mouse settings under Win10.

Ok, let me be more precise: it makes no fun flyin' the huey atm.

I hope that this issue will be fixed in the next OB. Makes no fun flyin' helis since several weeks. Transporting units is one of the main theatres of the huey and without the ability to embarking/disembarking troops he is nearly useless... :(

Due to the absence of a corresponding axis-command I don't think that you can bind your rotary buttons directly to the four trim-commands (nose up/down, left/right wing down). Maybe you can find a workaround using virtual joystick tools (i. e. vJoy & FreePIE).

Thx for your effort, Minsky! Now I have a little overview of the current status. :thumbup:

I've recently purchased the F-16C (thx @ED for the 50-%-discount!!!) According to the thread https://forums.eagle.ru/showthread.php?t=241132 my question: where I can find a current list with the already implemented systems & weapons for the F-16C?

Thx guys. I thought that I have to undesignate previous each single STEP to the next station... :lol:

I can confirm that behaviour, which is easy to reproduce: slave TPOD to a Waypoint slew TPOD to a target depress TDC to send coordinates to JDAM TOO pressing undesignate/nws button (obligatory to transfer next target's coordinates before pressing the STEP OSB) = caging TPOD to initial position

Check the settings for the throttle axis - maybe the "reversed"-box is checked.

There are Aliasing-Effects/Artefacts visible under certain view angles in the the external view (F2) - the issue is most extensive from the left and right view angle (around 90°). A screenshot of my grapical settings is available here: https://forums.eagle.ru/showthread.php?t=265969 Map: Caucasus DCS: 2.5.6.45317 OB nVIDIA-Driver: 442.59

Indeed. I've reported that bug already weeks ago, but it's still unfixed: https://forums.eagle.ru/showthread.php?t=264206 The Option to embark/disembark troops is simply missing in the radio menu.

Maybe because it's set to night-mode?

Already tested. No problems here with landing on the carrier (caught wire 4).

Indeed. TGP is really unhandy for the engagement of multiple targets in a single pass after the last OB (2.5.6.45317) Don't think there's a workaround available for that obstacle :(

Still unfixed in 2.5.6.45317 :( I dont' want to exit the OB and return to the stable due to that issue. Maybe it's an UH-1H-specific bug? I only own that one heli module atm...

Thx! Better late than never (fixed)! :)

:megalol:

Same behaviour here. I think, that's an issue. The entered TOT disappears sometimes after changing a WP, and sometimes it stays as desired. Map: PG OB 2.5.6.44266 352 FA-18C TOT Issue.trk

Seems to be a general problem with the new lighting system. The A-10C has this TGP-issue as well (https://forums.eagle.ru/showthread.php?t=265921)

Here comes the track showing the issue after ~1 min 506 UH-1H TerrainShadowsIssue.trk