Jump to content

omohat

Members
  • Posts

    49
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Given the J-8PP is a paper airplane and never saw service (or flew) it would be great it if you could give it a little more flexibility in the mission editor in terms of what ordinance it can carry so that mission designers can help match it with other Cold War aircraft in different scenarios. The J-8PP could stand in on Redfor in Cold War scenarios for planes like the Mig-23 but only if the weapon set is flexible (and not limited to late 80s/early 90s missiles only). The precedent for this would be for example the G91 devs planning on allowing Aim-9Bs even if the plane never successfully fired them IRL. So things like allowing R-3S (PL-2 proxy) and Aim-7E for early Cold War scenarios, R13M/M1 (PL-5B proxy) and Aim-7F for mid Cold War scenarios. I'm not for a second suggesting these are realistic loadouts but given how limited the plane set is in DCS, when it comes to PvP multiplayer scenarios we need as much flexibility as possible. Hoping Deka are open to this as it would massively help out in giving the J-8PP a home in as many Cold War scenarios as possible (rather than late Cold War/80s where its going to struggle against our late block F-16s/F-18s)
  2. I'd love to know this as well. I've tried this mapping on PvP Cold War servers with decidedly mixed results.
  3. It's been fixed in the last update (even if the change log didn't say anything).
  4. Thanks - can confirm that works and passes IC for MP
  5. Since the last update the jettison covers aren't working on the F1BE. Keybinds don't open them, nor can you click to open them meaning jettison is impossible and F1BE is essentially neutered for A-A on PvP servers
  6. Thank you so much for this - works perfectly! We've finally been freed from the tyranny of VR text size boxes
  7. +1 How can we select an alternative cockpit now since the Special menu option is gone?
  8. Since the last update I can't close the canopy on any variant (tested all 3) using the keybinds. The only way to close the canopy is by clicking. Anyone else facing the same issue?
  9. 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:
  10. J-8PP is going to be our Mig-23 stand in for the forseeable future
  11. OMG - thank you! I thought I was going crazy but yes I've seen the exact same issue.
  12. Ummm. DCS strikes again? I did the exact same steps in-flight and the waypoints are working. Not sure what was happening before.
  13. 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
  14. 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
  15. 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?
×
×
  • Create New...