Jump to content

rob10

Members
  • Posts

    3339
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by rob10

  1. Current issue with F-16 at low speed and any roll input. Happened in last patch.
  2. On further testing, it seems if you have it bound to a physical knob and the "sync controls on start" option checked, you may need to turn the HUD brightness OFF, then back ON. Seems to cue on the HUD actually powering ON rather than specifically the knob.
  3. It locks on contrast, so you may not have enough contrast with whatever specific point you're trying to hit for it to hit that. It's not really that level of precision weapon so you're not going to have MAV in force correlate mode accuracy likely.
  4. I've had it turned off since after about the 1st time it ran.
  5. One from mission 2: On the codewords kneeboard, the last entry (Felon I think) is a duplicate of one near the top of the page.
  6. That doesn't work simply because at different zoom level's the unit moves in relation to the ring (if you zoom out it will likely get closer to the ring because the scale goes up so 4 nm away may be shown a directly on top). I can confirm both the behaviour and need to adjust zoom to allow selection. Likely a rendering order thing, and the fix might have equally problematic unintended consequences.
  7. No worries. I think it's going to be a challenge to track down. In likely 10-15 attempts so far I managed to get comms to come up once. Fortunately I made it through the mission on that run . Quadruple checked the freqs (even made sure the presets were coming up with correct freq) and even turn off that preset and back onto it to see if that jogged it. Never use Easy Comms but I had gone in checked, closed, reopened and unchecked because I know that can be an issue. I had all mods (except Tacview and SRS (which wasn't running)) removed and did a full slow repair. Have never had Vaicom or voice attack installed. I'm running with a WinWing full MIP setup so SimAppPro running. I think that's about the only thing I didn't try without and just because I knew you were using a WW setup so I figured it wouldn't be that. Ping me if there is anything else I can do help you track down the issue. It can't be a complex trigger so there's got to be some weird little quirk on some systems not triggering it. And it definitely doesn't seem to be happening to many people.
  8. It's a function of the method of export that DCS is doing. All brands have the exact same issue. More power won't help brighten them (unless you really crank it up at which point it will be really bright for a very short period of time (and will likely make a big noise too) ).
  9. Unfortunately I've had that off for a long time now. Thanks for the suggestion though.
  10. That's what I mean. In my first flight I had that still turned on, and got an overspeed warning which stopped me in my tracks, but I had no problem getting going again after I put throttle to idle. Happened more than once on my trek to parking. But it was annoying so I turned it off after flight.
  11. I'd agree with this. At a minimum just keeping the enforced off only on this mission would be OK. I like my turbulence (except while it's throwing me around)
  12. I turned that off after my 1st landing, but TBH I got the warning about overspeed and came to an abrupt stop, cut throttle to idle and had no problem getting going again. I've seen a bunch of people reporting they couldn't get rid of them once they oversped, so I'm not sure what the difference is.
  13. Yes, trailing zeros. Just remember that it's 2 x 5 digit sequences so when your lead calls 9282 2758 you need to input 92820 27580, not 9282275800. Realistically you could enter 6 digit (928 275 (or 276 if you rounded up)) and probably be close enough to find a target visually. And make sure you set ELEVATION as 0 feet to get it to ground level (if you enter 0 it will adjust it to the appropriate ground level) or you'll be looking at the lovely clouds in the sky Also realize that in the very recent past the offset bearing entry has changed (won't be updated in the manual) and you now enter it as DDD MM SS. to the 75 degrees offset bearing gets entered as 075 00 00. You'll see the degree symbol on the UFC that will also help clue you on this.
  14. It's random. I managed to get the "F10 menu or tune freq" pop-up to come up when I tried it the morning and flew the mission. It was a lot of fun. But after I finished it I tried to run mission 1 a couple of more times and didn't get the pop-up. Also no F10 options showing without the pop-up so not possible to get around it that way. And the I and R windshield don't work without it either.
  15. Currently you cannot control the carrier in VR even if you are slotted into it.
  16. Carrier decides spawn points, you can't control where "live" units spawn on it.
  17. Which bindings are you using? If you want a single button to go both ways you'll need to use (for example) LMC SWITCH ON/OFF. Only use the LMC SWITCH ON<>OFF if you have it bound to an actual 2 way switch (rather than a button) and the LMC SWITCH ON and LMC SWITCH OFF only go to whichever you're using and not back and forth.
  18. If you're in CCIP but the HUD is showing AUTO that almost for sure means that you have a TARGET DESIGNATED. Nosewheel steer button to undesignate any target and you'll get your proper CCIP symbology back.
  19. QUESTION 1 - unfortunately yes. It's something ED has been working on for years but have also said for all that time that they were still looking for a solution and there was no easy answer (i.e. they're trying to figure it out, it's not just a solution that's waiting it's turn to be implemented when the devs have time) . The current solution is Reshade to adjust the brightness (esp. at night). You'll find posts in this subforum how to do that. QUESTION 2 - 1st thing to check is in your DCS settings, make sure you have the MONITORS set as "winwing". If you don't (i.e. it says 1 monitor) it won't pay attention to the proper layout and IIRC looks like what you described.
  20. And, should go without saying, the F-18. Mentioning that only in case you had uninstalled it at some point for space and forgot to re-add it before you tried this campaign. But Rudel_chw answer is 99% likely the cause.
  21. It's in the kneeboard that you can pull up in game. I'd also advocate for the kneeboards to be available as a pdf (and I think Baltic already indicated he was looking at doing so). In the mean time, if you open the .miz file (it's just a zip file), you can find the jpg version of those pages. your DCS main folder/Mods/campaigns/F-18 Arctic Thunder/ then open the mission you want it for. In the .miz file zip: KNEEBOARD/IMAGES and you'll find them there. You can copy them or print them as needed.
  22. Yep, tried all the different options including "fly again" from the debrief screen. Thanks for checking. This doesn't seem to be a widespread issue or I'd have expected to see more reports. That's the really confusing part. And it should be a really simple trigger so not a lot to go wrong with it.
  23. Not sure what's happening on your end, but an "always-on connection" still isn't required on my end. I just booted my DCS, then physically disconnected it from internet (it's got a wired connection and I double checked with a browser it wasn't connected) and flew for 20 minutes with no issue. Then I shut down my DCS and rebooted and got the normal sequence of "couldn't connect to server" and " you have a saved authorization valid for xxxx amount of time" and continued on and it worked completely normally with all my modules. Only time I've seen it boot me "login expired" has been when it was connected to internet and I had DCS up on my gaming computer and without thinking opened a 2nd instance on my laptop that I use for mission editing (or vice versa) and the originally running instance will get booted. It appears the issue is on your end somewhere and not something that ED has changed.
  24. I tried multiple restarts and it didn't help. Also tried flipping through radio presets (to ATIS and ground). Likely something simple that's not triggering, but I can't figure out what it is
×
×
  • Create New...