eFirehawk

Ouch, bummer. There goes 50 bucks. Thanks

Hi everyone, I'm considering purchasing this set: https://eu.winwingsim.com/view/goods-details.html?id=324&sku_id=30 However, there's one thing I'm having trouble to figure out. As you can see in the configuration above, I'd order the F-15E grip, which comes with the 'dual throttle connector'. What is the relationship between that and the Idle and AB detents? I have no interest in the finger lift kit they sell since the finger lifts themselves don't act as a button, so when starting up the F-15E, just touching them won't trigger the engines to start, making them just a mechanical unlock to move the grips. However, is the finger lift kit necessary in order to have Idle/AB detents? In other words, if I order the kit as is, with just the 'dual throttle connectors', will I have no detents anywhere? Thanks

The last waypoint was set as Turning Point in the mission editor. I tried setting it as Landing but no difference, always never present in the DST but the line to the ghost waypoint still shows up on the HSI. Is there anything specific that I need to set in the ME to make the last point show up in the DST page?

Added a proper screenshot, showing the HSD connecting to something after the last waypoint ( in this case, 7 ) to a supposed waypoint 8 that does not exist in the DST.

Hi everyone, I'm having a strange issue in which the last waypoint of the flight plan in the mission editor does not seem to exist in the plane, is not select able in any way, does not show up on the HUD, however it does show up as a final route point on the green, straight connecting route lines on the HSI. I don't understand why a waypoint from the mission editor is not considered, in theory does not exist, and yet its supposed ending location actually shoes up in the HSI. ( poorly drawn example here since I can't fire up DCS at the moment ) Waypoints in Mission Editor: 1--------2------3-------4---------5 HSI line: 1--------2------3-------4--------- Thoughts?

That did it, thanks!

Hi everyone, I'm able to navigate, create and edit waypoints in the Jeff. Very nice and easy to use, however there's one ( probably obvious ) thing I haven't figured out yet: If I click the Approach/Course/Bingo options in the UFC, my other waypoints and HSD lines between FP-A waypoints disappear and never comes back. I can only switch between APR/CRS/BNG but can't go back to FP-A. I can only see it again is to switch master modes. For example, if I can't access FP-A in NAV mode anymore, by switching to AA or AG mode it's still there, assuming I don't click the APR/CRS/BNG options there. So, how can I cancel the APR/CRS/BNG modes and get back to the Flight Plan A mode both on HUD and HSD? EDIT: For clarification, if I press RTN the UFC does show the 'FP-A' letters once again, but no effect on HUD navigation saying A0X steerpoint or any lines on the HSD. Thanks

Thank you very much for the detailed reply, much appreciated!

Yes, and what else exactly? For example, I really appreciate the F-15E because it's possible to do nearly everything without a WSO ( even though I understand it is completely unrealistic to fly without one ), radar included. At the other end of the spectrum, at least for me, is the F-14. I really don't like Jester and yet have to use him for many things. I wonder where would the F-4 fall between the F-15E and F-14 when it comes to pilot 'independence' so to speak.

Quick question: What can't the pilot do without the RIO in this variant of the F-4?

Any news on this? Also annoyed with the jumpy mouse cursor

Ah alright. I wasn't sure, that's why I didn't post on bugs. I will keep my eyes peeled for the next updates then. Thanks YoYo

Hi everyone, I created a fun little mission for myself in which I fly to an airfield to bomb a squad of bombers about to take off. They are guarded by 2 Shilkas. Obviously, when I approach the airfield the Shilkas pick me up so I get a SAM warning. However, after both are destroyed the SAM warning stays on, all the way even when I land back at the airbase over 150NM away. Absolutely no symbology anywhere on the RWR. Does the SAM Advisory need a reset or something? Apart from the Shilkas, no other objects on the map which could paint me. I have some static Comm towers but I doubt they have anything to do with it.

Hi everyone, So, I'm having a bit of a tough time doing elegant crosswind landings. Approach and initial touch down is not a problem, but once I have all wheels on the ground the rudder movements become too sensitive, making either the landings look very clumsy before the plane slows down enough or downright botched up - behaving as if I'd forgotten to turn NWS off in other modules. As I understand, in the F-15, nose wheel steering is always on, and the nose wheel steering lever simply increases the nose wheel angle in order to make the plane turn much faster for parking, so I suspect this could be the issue. Is there any way to disable it? Never had this kind of issue in any other module.

Wait a sec, so you're telling that the F-15E can actually trim itself? Have I been flying it wrong all along? I am away for 3 weeks so can't play DCS to confirm, but in no tutorial I remember anyone talking about the pitch ratio switch. So the condition for auto-trim to be enabled are: All 3 CAS switches to on, PLUS pitch ratio to Auto?

Hi everyone, In order to keep lasing the target after tossing a bomb, I have to keep ingressing into enemy territory. If I turn more than 30 degrees or so to either side, the TPOD gets masked by the stores a few seconds before impact, thereby ruining the shot. Any tips on how to deal with this? Any 'safer' way to keep lasing the bombs other than cranking just a few degrees? This is obviously more severe in cloudy missions that force me to stay under clouds in order to keep the laser effective.

Hi everyone, I'm having this intermittent issue where the TPOD sometimes does the correct thing, which is, as long as MARK is selected in the MFD instead of TGT, etc it creates a markpoint based on where the TPOD is looking at. However, sometimes even though I follow the exact same procedure, once I do a TDC press it creates the markpoint based on where the plane is instead, as if I would've pressed the MARK button on the UFC. Apparently what seems to cause it in my case are possible micro-movements of the TDC. I use a TM Warthog and it has the stupid 'nipple' type of TDC axis and press, so sometimes the TPOD moves slightly when I press the TDC, thereby creating the flyover points. It's hard to not move 'touch' the axis at all while pressing the TDC, although when I do 'perfect' presses without moving the axis at all it seems to behave correctly most of the time. Is this a bug or as intended?

Exactly, makes no sense to me either.

How do you create overfly markpoints? I don't remember reading about it in the manual, I remember only through TGP

@Timghetta In my case it's like you said. If mirrors disabled in settings, mission already starts with the 'low-res' mirrors which don't actually mirror anything, they just look like mirrors. I understand about the mirrors not being 'stowable'. Anyhow, maybe there's a chance that at least some F15s did not include the mirros themselves at some point? Anyhow, a bit off topic but since you're here... are you the guy who modeled/textured the F15E cockpit? If so... I am a modeler myself currently working in the automotive industry but did game assets in the past, and just wanted to say that your work is absolutely incredible and I can't thank you enough. Really, the work you did is absolutely exemplary. I did mess around with F15E_T0 and T3 textures ( in order to make the UFC's horizontal displays and letters consistently red and all frames the same gray ), and sometimes I couldn't help but to find myself just checking out all the little details in all the texture maps, and all the individual treatment of every single bolt being unique. Admirable work. Many many thanks! @ Everyone else: If enough of you guys show interest maybe I can try to make a mod, by assigning the parts of the texture maps which belong to the mirrors as transparent. I'm not sure of that will still make them reflective and shadow casting but I could give it a shot. This way, it could look like any objects related to the mirrors were never even installed in the cockpit. For realism, we could blame it on the virtual crew chief.

Agreed, I would love to have a 'mirrorless' cockpit as well or have the ability to stow them away.

By CPU you mean AoA, correct? Over 22 I think the flight path marker isn't visible anymore on the HUD so it gets difficult for me to gauge where I will touch down. Got tips for how to deal with that when landing heavy at 23 AoA like you said? Usually I still land with 21 even when heavy due to that inconvenience. I still can with 23 but it's not smooth and elegant most of the times.

I'd love to know as well... I also tried inverting the map colors by toggling the 'INV' function but makes it even worse, basically everything else in the map looks exactly the same as the green lines connecting the sequence points, making it impossible to distinguish them.

Hi everyone, I've been having this weird issue when trying to input a new sequence point, for example: N 41 41 393. Sometimes, the even if I input the number correctly, the last digit goes down by 1, so when I type in the scratchpad and then press button related to the latitude, the number shows up N 41 41 392 instead of N 41 41 393. That in itself isn't such a huge deal, but the worst is when it actually doesn't assign one of the first numbers properly, such as: Scratchpad input N 42 XX XXX becoming N 43 XX XXX. Obviously that ruins the flight plan. Anyone else having that issue or am I doing something wrong? If no one else is having it I will happily create and upload a track. Thanks

I'm wondering the same thing and would love to know as well.