Der F-14 Tomcat Diskussionsthread

[Lt_Jaeger]

1 hour ago, juvat22 said:

Also bei mir klappt´s immer noch nicht. Der AP koppelt sich zwar, 10secs kommt auch sauber, aber in der Regel entweder unsauber aufgesetzt oder hinten rein gekracht. Bis zuletzt schaut´s gut aus, aber dann muss ich eingreifen. Kann das so jemand bestätigen?

Nur wenn die Parameter beim koppeln schon nicht stimmen. Hab heute mal fix was ausprobiert und war dabei nicht auf dem gleitpfad. Danach ging s ganz schön ab

[BARRACUDA]

23 hours ago, juvat22 said:

Also bei mir klappt´s immer noch nicht. Der AP koppelt sich zwar, 10secs kommt auch sauber, aber in der Regel entweder unsauber aufgesetzt oder hinten rein gekracht. Bis zuletzt schaut´s gut aus, aber dann muss ich eingreifen. Kann das so jemand bestätigen?

Bei mir klappt es auch nicht... Schalte alles zu, aber wenn ich den NWS Button drücke, trotz das alles "ready" ist, passiert nichts... Schade...

[Lt_Jaeger]

3 hours ago, BARRACUDA said:

Bei mir klappt es auch nicht... Schalte alles zu, aber wenn ich den NWS Button drücke, trotz das alles "ready" ist, passiert nichts... Schade...

DLC draußen?

 

Das scheint sich wie ein Roter Faden durch das Forum zu ziehen.

Keine Ahnung ob es schon immer so war, ob es dem original entspricht, aber DLC gehört mE zur landing checklist und daher verstehe ich nicht, das es so viele nicht einsetzen. 

[QuiGon]

16 hours ago, Lt_Jaeger said:

DLC draußen?

Das!
Flaps müssen draußen sein und DLC aktiviert sein damit ACLS funktioniert.

[BARRACUDA]

23 hours ago, QuiGon said:

Das!
Flaps müssen draußen sein und DLC aktiviert sein damit ACLS funktioniert.

danke erstmal für die Hilfe!

DLC Toggle / Countermeasure Dispense meint ihr das? Wäre mir neu, aber ich schau mal, ob es damit funktioniert.. Was ist mit dem DLC thumbwheel forward und aft?

Edited June 3, 2022 by BARRACUDA

[QuiGon]

2 minutes ago, BARRACUDA said:

DLC Toggle / Countermeasure Dispense meint ihr das?

Jo

2 minutes ago, BARRACUDA said:

Was ist mit dem DLC thumbwheel forward und aft?

Damit kannst du das DLC dann manuell steuern wenn du es aktiviert hast. Am besten liest du dich mal im Handbuch in die Funktionsweiße des DLC ein:
https://www.heatblur.se/F-14Manual/general.html#dlc-direct-lift-control

[BARRACUDA]

1 hour ago, QuiGon said:

Jo

Damit kannst du das DLC dann manuell steuern wenn du es aktiviert hast. Am besten liest du dich mal im Handbuch in die Funktionsweiße des DLC ein:
https://www.heatblur.se/F-14Manual/general.html#dlc-direct-lift-control

Danke Dir!

[BARRACUDA]

4 hours ago, QuiGon said:

Jo

Damit kannst du das DLC dann manuell steuern wenn du es aktiviert hast. Am besten liest du dich mal im Handbuch in die Funktionsweiße des DLC ein:
https://www.heatblur.se/F-14Manual/general.html#dlc-direct-lift-control

Lag am DLC und funktioniert jetzt! Danke!!!

[QuiGon]

3 hours ago, BARRACUDA said:

Lag am DLC und funktioniert jetzt! Danke!!!

Das freut zu hören

Edited June 3, 2022 by QuiGon

[QuiGon]

On 5/16/2022 at 12:18 PM, MattDicker said:

Servus Leute,

ich habe jetzt paar mal die Täuschkörper ADM-141 eingesetzt. Aber irgendwas läuft nicht richtig oder ich mache etwas falsch.

Die ADM-141 klinken sich aus, aktiviert sich aber nicht. da die Gleitflügel nicht ausgefahren fahren werden und die SAM aus sie nicht aufmerksam werden.

Kann mir einer von auch hierzu eine Info geben wie ich diese richtig abwerfe.

Die ADM-141 sollte nun mit dem gestrigen OB-Update wieder funktionieren.

[QuiGon]

Dev-Update zur großen Phoenix-Überarbeitung, die mit dem nächsten Update kommen soll:

1 hour ago, Cobra847 said:

Dear all, 

As part of this patch, we are very happy to conclude a major overhaul of the AIM-54 Phoenix! This effort is intended to bring you significant improvements in realism based on new analysis and insights into the AIM-54, further enhancing realism and more accurately depicting air-to-air combat of this era.

Regrettably, our journey with the Phoenix is somewhat long, owing to the difficulty of simulating even older ordnance. In the end, our goal has, and always will continue to be, to achieve a greater level of realism across all facets of our simulation, even at the cost of some inconsistency over time, investment and time. We are not afraid to take a step back, further analyze and improve upon our work to bring all of us, and you, one step closer to the ultimate simulation of the F-14 and its trademark Phoenix. 

Over the course of this overhaul we gained many new insights and new knowledge, through new documentation and SMEs, that has increased our understanding of the AIM-54 missile, ultimately helping us to improve the simulation of this iconic weapon. It is a continued journey of discovery and learning, and we appreciate you all being a huge part of it and helping us to expand our knowledge and insights through your outstanding and unwavering feedback. Thank you! 

With this update, we believe that we’ve reached a point, where both -A and -C variants are depicted as close to real life as is possible with the current API/schema. Any further updates to guidance and features will have to come as part of a renewed effort to fill any remaining gaps that may remain.

On a general performance note, we’ve very thoroughly tested these changes, and have recreated all known test shots from 1972 and 1973 (with the -A) as part of our verification process. Every missile has strengths and weaknesses, and particularly with older missiles, one has to play to its strengths to not only make it work, but make it work consistently. In that sense- we will be very much looking forward to your feedback and results. 

We truly hope you enjoy the changes, both as F-14 drivers and otherwise, further detailed below:

Motors
Upon further in-depth investigation and consultations with SMEs, both the MK-60 and MK-47 motors were found to have somewhat incorrect performance. Of particular note is that with newly found data we’ve concluded that the MK-60 motor performance was too high, and this motor now more closely aligns with the other motors. 

Thusly, we’ve adjusted motor performance to levels which now more closely reflect real life performance as follows:

• MK-47 Mod 0: Reduced Impulse: burn time is the same but thrust is reduced.
• MK-60: Reduced impulse significantly: thrust is the same, but burn time is reduced to 20.6 seconds.
• MK-47 Mod 1 (originally the C motor): Impulse has been reduced to be the same as the MK-47 Mod 0, however this motor produces a reduced level of smoke.
• The MK-60 motor has been made available for the AIM-54C.

Guidance
As many of you have noticed, we’ve been working on guidance for the AIM-54 for the past several months- continuously improving tracking and terminal performance. 

In this update, we’ve continued this general guidance work, and all missiles have seen their proportional gain increased, yielding better terminal performance. 

Primarily as part of this overhaul however, we’ve made significant changes to both the -A and -C specific guidance models, which now gives a greater depth of simulation of both missiles, as well as differentiating appropriately. Specifically:

AIM-54A
The -A model of the AIM-54 is rather old, and unfortunately not very smart. This will now be more accurately reflected in the missile’s behaviour and how it guides on targets.

Reflecting the lack of internal guidance, the AIM-54A will now only track when the target is actively illuminated by the radar. This means the missile will only guide periodically in Track While Scan (TWS) mode. The guidance updates can be observed when viewing the missile in external view. Single Target Track (STT) will still illuminate the target constantly and as such the missile will guide the entire time. 

We’ve also reduced the chaff resistance of the -A to a level that we believe is more appropriate. Overall, the AIM-54A guidance will more accurately reflect being a product of its time and being limited in processing power.

Note the periodic guidance updates of the AIM-54A

AIM-54C
In stark contrast, the -C is a smart cookie and we’ve now been able to implement some additional features to reflect this. 

Importantly, the missile will now go active on its own. This is important as previously the -C had to receive a command from the aircraft, limiting its capability somewhat in situations where the shooting aircraft had to turn away. We’ve also reduced the chaff susceptibility of the AIM-54C, and added a MK-60 equipped -C variant due to motor interchangeability. 

One remaining small limitation is that in STT, the missile will erroneously go active on your target (it should remain semi-active all the way to target). This is unfortunately a limitation of the API at this time. We endeavour to model this behaviour properly in the future. 

Overall, we hope that you will enjoy this update and are greatly looking forward to your input and feedback. We believe we’re now one step closer to the ultimate F-14 simulation, and we’ll be continuing our efforts to get ever closer as we continue our journey out of EA.

The full changelog of the update is as follows:

DCS: F-14 Tomcat by Heatblur Simulations

• AIM-54 Overhaul, Part 2:
  • Increased PN gain for all variants.
  • AIM-54A will now only update guidance when the target is illuminated (you will see the missle periodically update).
  • Corrected motor impulse (reduced MK47 a bit and the MK60 significantly).
  • Reduced MK-60 burn time from 30 to 20 seconds.
  • Both motors have the same total impulse now. The MK60 has a slight advantage during motor burn time, while the MK47 has an advantage in burn time. With increasing altitude the difference becomes smaller. 
  • MK47 Mod 1 has now the same thrust/impulse and burn time as the Mod 0, but with reduced smoke (was previously weaker than the Mod 0).
  • AIM-54C should go active by default (even when losing lock from STT).
  • Increased AIM-54C chaff resistance.
  • Reduced AIM-54A chaff resistance.
  • Added option for AIM-54C with MK-60 motor.
  • Adjusted AIM-54 missile empty mass.
  • Adjusted MK-60 motor propellant mass.
     
• Set the JESTER option for automatic PDSTT -> PSTT to disabled by default.
• Fixed several issues with damaged avionics and flight systems (including jammed flaps for example) not allowing a repair to be triggered.
• Potential fix for CTD with F-14 AI (was not applied correctly in the last patch).
• Fixed emergency sweep logic:
• Fixed commanded wing sweep position being saved over to a new aircraft spawn.
• Fixed emergency wing sweep handle moving to spider detent on new aircraft spawn.
• Fixed wing sweep indicator commanded position bit mismatching with the actual indicated position.
• Fixed emergency sweep handle able to be moved between 68° and 75°, after being stowed at 75°. Now it has to be lifted to move it again after it has been stowed.
• Fixed wing sweep indicator raising EMER / OVER flags when wings get swept past 67 degrees.
• Fixed turn indicator needle deflection rate.
• Fixed mach buffet not dying off beyond M 1.3. 
• Fixed an issue with the AWG-9 track logic to avoid tracks being thrown by aircraft launching air to air missiles.
• Fixed LANDING CHK light remaining illuminated after touchdown. 
• Fixed Manual Throttle not unlocking after disengaging the Autothrottle.
• Fixed all mission versions of “Watching the Devil Dog” not being able to be completed successfully.
• Fixed VF-31 AE-200 and AE-205 1991 by Mach3DS - thank you. 
• Fixed VF-14 AB-100 and AB-103 1796 by VFlip - thank you. 
• Added Top Gun 114 by LanceCriminal86 - replaces previous Top Gun livery. Thank you.
• Updated Rogue Nation by YaeSakura - thank you.

Thank you!

Sincerely,
HB

 

Edited September 1, 2022 by QuiGon

[1stBEAST]

Ahoi liebe Tomcat gemeinde.

hat sich was am start up geändert bei der katze?

wir hatten gestern immer mal das problem das das HUD schief hingalso steig leiter im HUD war nicht gerade.

ich bilde mir ein das kätzchen nicht ge-over-g-ed zu haben da die video displays noch gerade waren.

war im mulitplayer mit human rio

Edited September 25, 2022 by 1stBEAST

[QuiGon]

On 9/25/2022 at 10:11 AM, 1stBEAST said:

Ahoi liebe Tomcat gemeinde.

hat sich was am start up geändert bei der katze?

wir hatten gestern immer mal das problem das das HUD schief hingalso steig leiter im HUD war nicht gerade.

Da hat sich eigentlich nichts geändert. Hing es denn schon beim Startup schief oder erst später?

  

On 9/25/2022 at 10:11 AM, 1stBEAST said:

ich bilde mir ein das kätzchen nicht ge-over-g-ed zu haben da die video displays noch gerade waren.

war im mulitplayer mit human rio

Over-G beim INS passiert bei der Tomcat schneller als man denkt, aber das sollte dir dein RIO beantworten können, denn bei dem leuchten dann entsprechende Warnleuchten auf.

[FR4GGL3]

Ich bin nun schon länger nicht mehr geflogen (bestimmt seit 2 oder 3 Open Beta Patches). Heute habe ich es wieder gewagt, weil ich testen wollte ob es da wirklich einen crash mit den neuesten nVidia Treibern gibt.

Was mir dann heute aufgefallen ist, ist dass ich wenn ich die Boardkanone im PLM Modus nutzen möchte, ich quasi keinen Piper mehr kriege. Zumindest nicht während ich schnell in einem Richtungswechsel bin (Kurve fliegen oder Vertikale, völlig egal - eben nur nicht geradeaus). Ich kann mich nicht erinnern, dass der Piper SO zäh war. Er war natürlich immer etwas zäh, aber nicht so wie ich es heute erlebt habe. Ich musste quasi aufhören am Stick zu ziehen und auch noch die Geschwindigkeit verringern, damit mein Piper wieder im HUD erschien.

Ist das mittlerweile eine Neuerung und soll so sein, oder stell ich mich mal wieder zu blöd an?

 

//edit: hat sich erledigt. Nach einem Rundumschlag (Reparatur, Caches löschen, Reboot) ist das Verhalten am Folgetag wieder so gewesen wie früher. Keine Ahnung was da los war.

Edited October 14, 2022 by FR4GGL3

[QuiGon]

Dev Update

1 hour ago, Cobra847 said:

Dear All,

Another major F-14 update is about to drop!

One of the biggest features we’ve developed since launch for the F-14 is coming with today’s patch; namely expanding and extending our radar simulation to encompass Jamming and associated EW effects and their impact on the AWG-9- but we’re also shipping more features such as new JESTER functionality for mission editors and the in-cockpit VR pilot with this patch.

Lets kick things off with a deep-dive into the biggest feature to drop, namely Jamming and Jammer Tracking for the AWG-9

 

NEW FEATURE: Jammer Effects, Detection & Tracking in the AWG-9
 

This new feature will now enable accurate effects on the DDD and TID for jamming, tracking jamming targets and guiding missiles on these targets, as well as any associated ancillary effects that we feel make sense to model in the DCS environment. Here’s a breakdown of some of the things you should expect:

In summary, noise jammers prevent the AWG-9 radar from ascertaining (and therefore displaying) range or range-rate information on a target, until burn-through is achieved (when the radar return signal is sufficiently strong to overcome the received jamming noise). The AWG-9 has several features which allow the aircraft to still be effective against such threats, which we can detail further below;

The DDD will show noise returns over the range axis at the azimuth of a jammer in pulse search mode, which looks something like this:

In Pulse Doppler modes, the DDD shows a jamming intensity trace overlaid on the lower one-third of the display. This is essentially a graph of received wideband power vs. azimuth, and thus also shows smaller normal radar returns. 

Where a noise exceeds a predetermined threshold, a JET (Jam Exceeds Threshold) vertical strobe is also displayed on the DDD at the jammer azimuth.  Note that due to what we feel are justifiable DCS limitations in jamming fidelity, the JET (Jam Exceeds Threshold) settable knob is not implemented at present.

Here’s what this kind of intensity trace can look like on the DDD:

Jammers will show up with a jamming strobe (straight line in the direction of the detected jamming signal) on the TID in TWS and RWS modes, these can be toggled with the Jam Strobe button beneath the TID. If range/range-rate is not available for the jammer (beyond burn through), an angle symbol (<) is displayed on the strobe at 50NM from your aircraft.

The jam strobes are also shared over Link-4A fighter-to-fighter datalink, allowing for eyeballed triangulation of actual jammer position, an example of which looks like this:

The TID angle symbol is hookable, to allow the RIO to try to get an STT lock via the PD-STT or P-STT buttons. The HCU radar cursor can also be used in the normal fashion on the DDD to try to acquire jamming targets in PD search or P search. We’ve extended JESTER functionality to also allow him to lock jammers ahead.

Practically speaking, when a jammer is locked in any of these scenarios, it leads to a special STT submode named Jam Angle Track (JAT). In JAT, the range/range-rate of the jammer is unknown, but the angles are known and can be tracked as such. 

Instead of the RDROT (Radar On Target) light above the DDD, the JAT light is displayed in this case. On the TID, the angle symbol (<) is displayed along the jam strobe at 1 inch from own aircraft position in STT-JAT modes. When burn-through is achieved, the angle symbol will disappear and be replaced with the normal target symbol at the correct position. Conversely, if an STT target starts jamming (and is beyond burn-through), it will automatically transition to STT-JAT submode.



In STT-JAT sub-modes, both AIM-7 and AIM-54 can be employed in Home On Jam (HOJ) modes. Since range is unknown, lofting is disabled, and the missile guidance is similarly limited to only using angle information to intercept the target.

HOJ launches are therefore limited compared to normal STT launches, but in the end, better than nothing.  

With this update, we hope to take another large step forward in our simulation of the AWG-9 radar and associated systems, and bring us far closer to a fully realised picture of what utilising and operating this radar system was like in a live combat environment. 

The effects described above and the associated functionality in the AWG-9 will have to be accounted for by all RIOs and JESTER, and significant changes in how you approach various situations may be required. We’re proud of our work on simulating this aspect of the AWG-9 and greatly hope you will enjoy flying and fighting not only enemy bandits but also their emissions.
 

New & Expanded Feature: JESTER Custom Commands

We love supporting all the wonderful and talented mission and campaign-builders out there in the community. One of the great things about multi-crewed aircraft is that it can bring a sense of immersion that single-seat aircraft can’t- and JESTER is a big part of that for the F-14. Over the past few months, we’ve invested significant time in extending JESTER’s functionality but also giving mission makers deep hooks into JESTER to enable you to control the RIO at a granular level and make this a key part of your narrative toolset.

Succinctly, we’ve added a large number of commands which let JESTER perform actions on his own, at the behest of the mission designer, without the player’s input, which can help drive a scripted narrative or create the illusion of him being an autonomous RIO who both thinks and acts on his own in the context of pre-planned situations. These set commands can be triggered in the mission editor as actions, following the entire range of conditions provided to the mission creator in DCS, from unit inside zone, to flags being true, etc. 

The first major addition to these were the LANTIRN set commands, which we demonstrated in the mission “Training Day” - they let JESTER scan zones, track targets, designate and undesignate whatever is in the crosshairs, and thus help create the impression of the RIO pro-actively searching an area and fulfilling his mission to locate, track and engage a target. Additionally we gave mission creators the ability to make him go silent or talkative again, so that mission-based voice acting does not cross over with the normal JESTER comments that are situation-based and can conflict with scripted dialogue at any given time. 

We’ve also added the ability to make JESTER change channel presets for the AN/ARC-182, tune TACAN channels on his own, change steerpoints, create steer points from coordinates belonging to a trigger zone, to set the WCS to on, off or standby, manipulate the TID range knob, perform an RWR test and even have him eject on the command of the mission creator. With this latest update, we are introducing even more set commands to further the mission creator’s abilities. He will now be able to select weapon stations, set the weapon selector wheel to a preselect and desired weapon for air to ground missions, set ripple quantity and interval as well as all additional delivery modes, he can set attack modes like computer target, computer pilot and manual. Furthermore he can now manipulate the radar scan zone in elevation and azimuth, he can STT a specified target (and break lock again), and also perform a missile launch if the mission creator so desires. 

To give you some insight into a “on the ground” usage of these tools; here’s what the wonderful Reflected had to say about using this new functionality in the upcoming “Speed & Angels” campaign!
 

To guide you through using these tools, here’s a tutorial video from Reflected himself running you through how to use these tools in your missions.

 

We greatly hope you’ll enjoy using these new JESTER tools to craft immersive, guided and curated experiences for the Tomcat.
Check out the full list of commands here:   
https://forum.dcs.world/topic/311033-jester-set-commands-full-list/

 

New Feature: In-Cockpit Pilot

Last but not least; we’re finally implementing in-cockpit pilot bodies for both the Pilot and RIO positions. These new pilot models were sculpted for the purpose of not only serving as cockpit bodies, but will eventually replace the current lower detail bodies in exterior view and in the cockpit for the other crewmember. This will however be added at a later date. We’ll be adding more customization functionality as we go.

 

null

 

The non-exhaustive changelog for the F-14 in 2.8 looks as follows:

DCS: F-14 Tomcat by Heatblur Simulations

• NEW: Introduced Pilot and RIO body for front and back cockpit. 
   
• NEW: Added jammer detection and tracking functionality in the AWG-9, which adds amongst other features:
  • Noise jammers will now prevent AWG-9 from ascertaining range or range-rate from a target.
  • DDD will show noise returns over the range axis at jammer azimuth in pulse search. 
  • DDD will show jamming intensity trace overlay in pulse doppler modes. 
  • TID will display jamming strobe in TWS and RWS modes. 
  • TID jamming strobe can be toggled via Jam Strobe button below TID.
  • Jam strobes can be shared over Link-4A fighter to fighter datalink, allowing for eyeballed triangulation of actual jammer position. 
  • TID angle symbol is hookable. 
  • PSTT or PDSTT on jamming target leads JAT (Jam Angle Track).
  • STT-ed target transitioning to jamming outside of burnthrough automatically switches to JAT submode. 
  • In STT-JAT submodes both AIM-7 and AIM-54 can employed in HOJ (home on jam). 
     
• Added jamming targets to JESTER STT options. 
   
• NEW: Added new list of set commands for JESTER to be used in the Mission Editor.
  • 10017 to 10033 are new.
  • For a full list visit this post here. 
     
• Reverted AIM-54 loft to state before looping hotfix to revert exceptionally poor performance.
• Fixed forward rendering for canopy sealant - will now not appear shadowed at odd angles anymore.
• Screens and other glass surfaces will now reflect sunlight again.
   
• Added non-gfx external args to check the status of JESTER tracking air targets (to be used with scripts):
  • 1026: tracked predefined target; 0.01 - 0.99, same as command 10024; 0.0 - no predefined target tracked.
  • 1027: range to predefined target (only when tracking); 0.xxx - three digits of distance to tracked predefined target in NM.
     
• Potential fix for mission freeze including F-14 AI. 
• Made LANTIRN available as laser designator for the AI. 
• Fixed ALT HOLD not working >36k AGL. 
• Fixed flashbang-like sun glare on internal canopy glass.
• Fixed MiG-23s not taking off in PG Flogger Faceoff Mission. 
• Adjusted all Quickstart BVR missions for new AIM-54s. 
• Removed instances of “color” shader in cockpit due to deprecation
• Minor cockpit optimizations - fixed some visibility arguments not triggering LoD changes
   

Thank you all for your support. We hope you’ll enjoy this update to the F-14 in 2.8; and we look forward to sharing more on the F-4, Eurofighter, Viggen and others very soon!

Sincerely,
Team Heatblur

 

 

[Gizmo03]

Danke für die Info, Quigon.
Ihr mögt mich jetzt als Vollidioten sehen, aber das von mir sehnlichst erwartete in diesem Update ist dieses:

vor 6 Stunden schrieb QuiGon:

New Feature: In-Cockpit Pilot

Ich weiss: Killefit, aber ich find's extrem wichtig

Oh, edit: Damit will ich all die anderen Änderungen natürlich nicht runterspielen - generell ein toller Changelog für die Tomcat

Edited October 26, 2022 by Gizmo03

[QuiGon]

17 minutes ago, Gizmo03 said:

Danke für die Info, Quigon.
Ihr mögt mich jetzt als Vollidioten sehen, aber das von mir sehnlichst erwartete in diesem Update ist dieses:

Ich weiss: Killefit, aber ich find's extrem wichtig

Oh, edit: Damit will ich all die anderen Änderungen natürlich nicht runterspielen - generell ein toller Changelog für die Tomcat

Ich bin froh, dass endlich Jamming-Effekte kommen. Das hat mich all die Zeit tierisch gewurmt, dass die Tomcat gegen Jamming total immun war.

Mit einem Piloten-Model weiß ich hingegen nix anzufangen. Der verdeckt mit seinen Armen nur lauter Schalter, an die ich dann nicht mehr dran komme

Edited October 26, 2022 by QuiGon

[Gizmo03]

vor einer Stunde schrieb QuiGon:

Mit einem Piloten-Model weiß ich hingegen nix anzufangen. Der verdeckt mit seinen Armen nur lauter Schalter, an die ich dann nicht mehr dran komme

 

Ich sag ja: Killefit im Grunde genommen - zumindest für die meisten. Für mich nach wie vor extrem wichtig

[derneuemann]

Moin, mal just ne Frage. 

 

Ich höre den normalen Spielsound, nicht aber Jester höre ich nicht, auch meine eigenen Funktsprüche zu Jester und auch zur Bodencrew höre ich nicht. Kennt das einer? 

[Charmin2105]

vor 42 Minuten schrieb derneuemann:

Moin, mal just ne Frage. 

 

Ich höre den normalen Spielsound, nicht aber Jester höre ich nicht, auch meine eigenen Funktsprüche zu Jester und auch zur Bodencrew höre ich nicht. Kennt das einer? 

Man kann in den Optionen den Audio Ausgang für den Funk auf andere Geräte setzen. Ist mir zumindest mal passiert

[derneuemann]

vor 1 Stunde schrieb Charmin2105:

Man kann in den Optionen den Audio Ausgang für den Funk auf andere Geräte setzen. Ist mir zumindest mal passiert

Jao, danke. Ausprobiert, funktioniert. Habe aktuell drei Monitore am Rechner und eine andere GPU drin. Da funktionierte Standard irgendwie nicht mehr.

 

Danke

[JG11Preusse]

Kurze Frage:

Wenn ich DLC aktiviere, gibt es im Cockpit eine Anzeige, wo ich sehen kann, ob es aktiviert oder deaktiviert ist ?

 

Gruß

Andi

[razo+r]

5 minutes ago, JG11Preusse said:

Kurze Frage:

Wenn ich DLC aktiviere, gibt es im Cockpit eine Anzeige, wo ich sehen kann, ob es aktiviert oder deaktiviert ist ?

 

Gruß

Andi

Ja, es gibt eine Anzeige links am vertikalen Panel die dir anzeigt, in welcher Position die verschiedenen Steuerflachen sind.

Edited November 10, 2022 by razo+r

[JG11Preusse]

vor 20 Minuten schrieb razo+r:

Ja, es gibt eine Anzeige links am vertikalen Panel die dir anzeigt, in welcher Position die verschiedenen Steuerflachen sind.

 

Danke schon mal.

Und dort erkennt man sofort, ob DLC aktiviert ist, auch wenn ich die Manöverklappen bei Flaps up benutzen möchte, aber straight and Level fliege oder Flugmanöver durchführe, denn dann bewegen sich die Steuerflächen ja eh ?

Bei der Landung mit Flaps down ist das ja kein Problem

[razo+r]

Alle Steuerflächen und deren aktuelle Position sind abgebildet. Falls du daher es irgendwie schaffst, die DLC mit Flaps up zu nutzen, was eigentlich nicht möglich sein sollte ausserd du meinst die Spoiler allgemein, wirst du das auf der Anzeige sehen.

Edited November 10, 2022 by razo+r