omohat

I just finished a Monster Rhino kit bought from @Winger to replace my OG Rhino and can't stress enough what an absolute quality piece of kit it is. Also @Winger does a greta job of supporting through the build if you're less than confident about anything (like me) so that helped massively. I put a more in depth review on the Hotas subreddit in case you want more details:

J-8PP is going to be our Mig-23 stand in for the forseeable future

OMG - thank you! I thought I was going crazy but yes I've seen the exact same issue.

Ummm. DCS strikes again? I did the exact same steps in-flight and the waypoints are working. Not sure what was happening before.

Ah ok. Let me RTFM again and re-try. I'll report back with a track if I still can't get it to work

Is there some special process for adding INS waypoints in the mission editor for the F1EE? When I add waypoints, the only waypoint the INS actually has is the aircraft starting position (verified because I can see the wide needle point behind me and the distance increases). The IDN is in NAV-N mode When I select waypoint 2 and press * the distance in the IDN disappears (even though the INS display is showing waypoint 2). The wide needle points to 270 and the distance counter shows 999 What am I doing wrong (not doing) in the mission editor when setting up waypoints. I've attached a mission showing what I've tried to setup (air start with 2 waypoints; i.e. should be three waypoints stored in the INS) 03 Caucasus INS ME Waypoint Test.miz

Thanks for this - that solves most of the missing pilot bindings. I have a follow up question though - is there a similar file for the RIO which shows how to keybind some of the missing items there like Liquid Cooling, RIO oxygen, datalink TAC/Norm?

Has the code expired now?

Given this was a prototype/paper plane it would be good if Deka took a slightly more liberal view of the available A-A weapons to ensure it has the best chance of fitting into different eras in the DCS scene (e.g rear-aspect Fox2 for the early cold war as well as all aspect Fox2 and Fox1 missiles for mid-cold war)

I was looking in the control bindings for the QNH dial (to set altimeter pressure) and speed bug but couldn't find any bindings for these. Am I looking in the wrong place or are there no bindings for these? I'm pretty sure I tried searching for terms like: QNH Baro Pressure Speed Bug but no luck. Appreciate it if someone could advise/help.

Amazing - thanks and look forward to seeing it in the next patch!

Exactly as per the title; the key binding for the fuel quantity reset wheel only allows you to increase the amount of fuel. But if you release your drop tank early in the flight (about to get jumped) there's no key binding to bring the fuel amount down to reduce the amount to what you actually have meaning you'll inevitably run out of fuel because you'll forget to subtract the right amount from the remaining fuel. Given the wheel can move in both directions shouldn't we have a key binding for this please? Hopefully it should be easy to add!

Yes please - Aegean Ghost as one of the default skins would be fantastic!

Thank you for returning the AZ/CZ skins - they've always been some of my favourite F1 skins. It looks like they're back just for the CE though - any chance they could be enabled for EE as well (the advantage of you doing it at your end is that on multiplayer servers others will see the same skin [as opposed to just me seeing it if I do it]). One small additional livery request - any chance you could add the low viz half camo/half grey SAAF scheme like this one: https://www.digitalcombatsimulator.com/en/files/3340854/ This was always a favourite of mine for this plane. I'm hoping it wouldn't be too much trouble.

I'm Dubai based and looking for a regular wingman - but I fly Cold War rather than modern/4th gen airframes. DM me if you're interested in a wingman for ECW or Contention. Internet speed is excellent and will cost you about 400AED/month for a high speed connection. There's only 2 internet providers, they cost virtually the same and in many areas one of them will have a monopoly so you don't have much choice. I get a ping of 100-150ms to EU servers and 220-300ms to US servers - both are playable without significant lag (The above is for wired [fibre] internet. You can also get 5g based home internet but I believe the cost is similar but no idea about speed/latency) VPN isn't needed to play per se - but is needed if you want to use Discord for voice comms (although SRS will work without VPN) I use a VPN when I'm playing with randos and we're on Discord but if I'm playing with someone I know, I'll use google meet to avoid the hassle of the VPN

Thanks for raising this. Hope Aerges come back with a response

OMG - this has been bugging me. I couldn't for the life of me work out why the velocity vector kept randomly disappearing but this was it. Thank you!

Ok thanks. I'll try that. Based on what you've said I was probably too high to catch the glideslope. Anyone have any tips on TACAN offset in the EE? That one is still vexing me.

Ok. So then use TACAN (or VOR) to line up with the runway radial, and then ILS (autopilot G mode) to capture the glidescope? I guess the process would look something like this: Set TACAN channel Tacan to T/R Set omnichannel bearing to runway course Set omnichannel source to TACAN Autopilot on and R mode armed Once runway radial is captured and being flown, start descending to capture the glidescope Configure ILS frequency ILS On (Marche) Set omnichannel source to VOR/ILS Autopilot G mode armed (do I have to turn off R mode or will it be turned off automatically when the glidescope is captured?) Wait for glidescope to be captured; then manage throttles to control AoA Is that right?

Ah ok - didn't know that.

I'm guessing this fix didn't make into yesterday's patch? I'm still finding the green (right wing) light won't switch off.

Yes because when I'm using TACAN for navigation the ADI is showing the yellow course line correctly (selector is "up" for TACAN). When I want to switch to VOR or ILS I move that selector to the bottom VOR/ILS position

I'm trouble with a few of the instrument navigation tools and despite checking the manual and youtube I just can't figure out what I'm doing wrong. Issue #1 (F1CE & F1EE) - VOR/ILS I can tune in a VOR/ILS station (correct frequency and VOR to Marche). I can hear the morse code from the station (TACAN volume is turned off so it has to be the VOR/ILS station) but I can't get the VOR station bearing to show up on the IDN (in the CE I've selected VT mode and in the EE I've selected RNAV-N and switched the Narrow needle selector to VOR). Despite this, in both the CE and EE the VOR needle stays stuck to N indicating it's not picking up a signal (despite me hearing the morse code from the station). As a result I can't intercept the glidescope for an ILS approach. It's driving me nuts. What am I doing wrong? I've got no problem tuning and navigating off TACAN stations (including course/omnibearing and using the Autopilot to "catch" the omnibearing course) Issue #2 (F1EE only) - TACAN offset I can configure TACAN offsets in the CE fine but in the EE no matter what i enter for distance and angle, when I switch to RNAV-VA it doesn't seem to reflect the offset distance and angle in the IDN. Not as annoying as the above issue because in the EE I can always configure an INS waypoint for the offset position but i don't understand how I'm doing it correctly on the CE but same thing on the EE doesn't work. Any ideas?

I literally came here to report this bug with the right (green) light no switching off. Glad to see its already in hand - shame we'll have to wait ~6 weeks for a fix. Just going to have to remember not to turn on any lights while on a PVP server.

So as an example I have a SP offline mission I've created where I'm looking for bombers about 80 miles away. With a human WSO its no issue - he puts the radar into 100 mile and then starts working the gain until we can see some faint returns. We then head towards those returns until the target is close enough to lock and then we can start tracking and setting up for a missile shot. The same mission with Jester I've got no way of locating targets beyond 50 mils. I understand you don't want pilots "playing WSO" but perhaps something in the Jester menu to convey context to Jester to get him to change his normal behaviour rather than outright commands? e.g. "Looks like our bogeys are a long way out" = Try 100 mile search? or "Bandit is closing fast" in Boresight or Cage = Set Aspect knob to Nose or Fwd and you can introduce a little randomness into it to convey the fact that its a team working together rather than the pilot treating Jester like a command menu wdyt? Keeps the immersion while allowing us to guide Jester a little more to what we want?