Jump to content

Shiroka

Members
  • Posts

    195
  • Joined

  • Last visited

Everything posted by Shiroka

  1. Is that not what I’m doing in the track? I’m pretty sure I’ve tried it every which way and I just can’t get anything working. Same with Alt Select. i posted on the Discord and got nothing useful back, it seems like it works for some people but I don’t know what the difference is. Only thing I can think of is single-thread vs multi-thread (I use multi) but that’s a total guess.
  2. I'm in the same position as the posters above. Cannot for the life of me get alt hold or alt select working. Current OB, multi-core. I've RTFM multiple times. Here is a track, I can't think what I haven't tried. Any advice appreciated. F-15E Autopilot.trk
  3. Not sure about the F-14 but for the M2000 this is correct, the only authorized CCIP release profile is a low level <650ft AGL 500 knot level release. CCRP (CCPL) has dive-dive, dive-level, and dive-toss releases. It’s in the manual.
  4. I’m getting the same with Mk-81s and Mk-82s. Dropping at 500kts, 6000ft in a 30° dive, falling consistently about 20m short with AUTO (whether I predesignate or CCIP -> AUTO convert, no difference). CCIP is spot on.
  5. Steps to reproduce: Set Flares mode "S" > release flares program (CMS Fwd) > hit "Flare Salvo": Salvo is fired Set Flares mode "P" > release flares program (CMS Fwd) > hit "Flare Salvo": Salvo is fired Set Flares mode "M" > release flares program (CMS Fwd) > hit "Flare Salvo": Salvo is fired Set Flares mode "G" > release flares program (CMS Fwd) > hit "Flare Salvo": Nothing happens Set Flares mode "R" > release flares (CMS Fwd) > hit "Flare Salvo": Salvo is fired Can be fixed by setting another flare setting (S/P/M/R) and firing a program before hitting salvo again. I'll add a track when I can create a short one.
  6. I agree, it’s easy to fix though as it’s like a 1 line mod. I’ll send you the details later today (not at my computer now). Easier, you can do it yourself. This mod for the AV8B (which unfortunately doesn’t work any more since they took out the visor) - just find the relevant changed line and put it in the M2k lua https://www.digitalcombatsimulator.com/en/files/3067866/
  7. My understanding (and hope) is that now it is open source it will be free! I’m sure the community is excited to be able to keep working on it as freeware (though I’d happily donate if there is a patreon or something). Personally I’m more than happy to have paid @Hollywood_315for his awesome work at the time and have got plenty of use out of it over the last 18 months so don’t begrudge a penny! I’m pretty sure most people feel the same way! Also to jump on the bandwagon and add my thanks to the both Hollywood and the community for keeping this amazing tool alive!
  8. Hmm so this got me thinking, what happens in the lua files for those radio commands with keybinds? People have added keybinds for missing commands before (see Quaggles DCS Input Command Injector and the community keybinds) - does it say activate an argument that you could mess around with to see if a different value is a different command that isn’t mapped? Not at my PC now but may be worth a play.
  9. Awesome, thanks for the fast reply. Really glad to know it is on the cards for the future! From a personal perspective I would rather deal with a broken VA profile every few updates than not have that functionality for months, but I do understand the devs decision (and of course don’t know the full situation)! Thanks again.
  10. For those of us who fly in VR, many of us have been using VAICOM to control Jester without the RIO wheel (which is great but kind of breaks immersion). VAICOM has been abandoned for months and it appears that 2.8 was the final death knell. It’s a real shame to lose this functionality and personally I don’t want to go back to the wheel in VR. Would it be possible to make the full Jester command set mappable to keybinds (as you guys have done with the Mission Editor values, which is awesome) so that those of us who want to continue using VA to talk to Jester can create our own profiles and continue to do so?
  11. So I’ve been having great results running the OpenXR toolkit (3090, G2). Looking through the forums I can see a lot of info on tuning for FPS etc, but no one has really mentioned anything about the post-processing options (vibrance, highlights, contrast etc). Obviously these act as a sort of pseudo-reshade in OpenXR. Does anyone have any good profiles/settings for this that they use to improve the visual effect (it’s something I’m not very good at, don’t even know where to start)?
  12. Hey @BIGNEWYcan we get the tag changed on this - I think the track clearly shows something is not right and I beleieve my discussion of negative numbers (which was just meant to help explain what is going on behind the scenes) confused the issue I was trying to report somewhat (apologies for this). I reproduced it and added a couple of screenshots below: First two images are expected behavior (by entering "90" in the O/S BRG on the UFC): Now if you enter "090" in the bearing on the UFC, the data page still says "O/S BRG 90..." but you can see the O/S grid has changed (from BN696062 to BN326050) and now the OAP appears in the wrong place W of the WYPT: There is no way that can be "correct-as-is" (the simple fact that both data pages show OAP range 10nm, bearing 90 but with wildly different grids 20nm apart)
  13. @BIGNEWYtrack attached here. In the first case I enter a bearing of "90" on the UFC. You can see the OAP is positioned correctly to the East of the waypoint. Then I repeat and enter "090". Now the data page still says the bearing is 90.00.00 but the OAP is incorrectly placed at 270 (West of the waypoint, i.e., at -90). FA-18C OAP.trk
  14. Thanks @BIGNEWYI get that, the problem is that if you enter a bearing with a leading zero (I.e., "090" rather than "90") it reads it as a negative number and inputs it as -90. Yeah I thought for ages that it wasn't working and was just giving me a completely random OAP. Then I sat down on the runway and entered a few values to try and work out what was happening behind the scenes. I didn't save a track (I turned off recording to try and save some FPS) but I'll reproduce with a track and upload next time I get a chance.
  15. Not sure if this is correct behavior or a bug, but I was having trouble entering OAP. If you enter an O/S bearing < 100° as a 3 digit number the first 0 is registered as a - (which I assume is correct behavior as the UFC panel shows a - on that button). However, there is no indication anywhere on the UFC or HSI that this is happening. Took me ages to work out why my OAP was in the wrong place. For example if you enter “090” then the bearing is registered as “-90” and the OAP appears at 270°. is this correct or should there be an indication on the UFC that you are entering a negative number? No track yet but I’ll try and get one.
  16. So as I understand it, the limiter on the AV8B is turned off when the throttle is pushed forward to the max (there is a sort of soft/elastic detente which requires a certain forward pressure to trip). This is (currently) not simulated but depending on your throttle you can replicate it. I have a Virpil with a physical afterburner detente that I don’t use on the AV8B. So my throttle goes to max when I hit the detente, but I also assigned that region of the throttle just past the detente (via a virtual button) to JPTL off switch. Just one way of doing it.
  17. That’s the FLIR hotspots. Super useful for picking up ground vehicles (not sure how they work with EDs new FLIR mechanics or if they are going to be updated, but before there was random “noise” simulated along with any actual hotspots). You can disable them from the FLIR page on the MPCD if you really don’t want them but I can’t see why you wouldn’t. TL/DR - feature not bug
  18. Great guide - this is exactly how I did it (though you’ve explained it better than I could). I have my “request control” binding and modifier toggle set up next to each other on my throttle so I hit both at the same time when I want to switch to flying.
  19. You can overcome this with a bit of creativity in the Virpil software. I assume you are talking about the flip trigger on, say, a constellation where the physical switch is pressed if the trigger is up? You can assign two logical switches to the same physical switch and set one to inverse such that one logical is “pressed” when the trigger is up (that’s your open) and one is “pressed” when the trigger is down (that’s your close). That’s what I’ve done and it works fine for me.
  20. I solved this by assigning a modifier switch to CPG bindings for all the cyclic and collective controls - right next to the switch I use for request control. I hit both at the same time then when I take control from the front seat all of my HOTAS commands and axes switch from TEDAC to the same cyclic and collective controls I use in the pilot seat. Took a while to set up but it works great, and I guess IRL you only have 2 hands so they are either on the TEDAC or cyclic/collective. for more detail I have a Virgil CM3 and I use the mode dial, mode 1 is TEDAC, mode 2 the modifier for cyclic/collective, I use press on one of the encoders immediately below it as the “request control”. I hit that button and flip the mode switch at the same time.
×
×
  • Create New...