Jump to content

Shimmergloom667

Members
  • Posts

    1115
  • Joined

  • Last visited

Everything posted by Shimmergloom667

  1. No, there is not. Only thing that apparantly *IS* a bug (afaik), is that the ADV-line should disappear completely, when there are none (which is not the case anyway, in your screenshot).
  2. This is my setup for the time being. I am not using the Saitek / Logitech software, since it is pure and utter crap.
  3. It *is* still probably "only" visuals in a very complex module, and I am guessing they will continue working on other stuff, first, is all I'm saying.
  4. IRL it should be (or very similar to) FS36375 Light Compass Ghost Grey.
  5. It's also probably just visuals, why it's probably low on the to-do list
  6. Refueling in a bank is honestly the same as refueling in straight line, only banked. Look for the same cues and just jam it in there.
  7. It's a confirmed bug that will be fixed in the next update
  8. No? https://forums.eagle.ru/showthread.php?t=242508&highlight=afterburner
  9. That's correct, both altimeter and variometer are inaccurate during transonic and return to normal when you are fast / slow enough again.
  10. https://skyvector.com/airport/UGSB/Batumi-Airport Rwy 13 has magnetic heading of 126°, so with the MVAR in the Caucasus region 120° true heading would be correct.
  11. Hm, I *just* came in from landing, pretty loaded at 36k lbs total weight, onspeed was roughly 140 - 145 KIAS. Persian Gulf, so pretty much around sea level.
  12. Given that our -B is no DFCS aircraft, but an AFCS aircraft... why should DFCS-behaviour apply to it?
  13. I'm using one of the small thumbwheels on the throttle of the X56, so you don't have to fiddle with the axis of the throttle being all over the place, trying to reach buttons.
  14. Ahhh, I see! I was wondering if it still was WIP, thanks for the heads up, baltic_dragon! :)
  15. Hey guys! So I went back to the Harrier after the load of updates lately, and for the love of my life: I can't get the TDC on the HUD to slew. I am in the appropriate training mission right now, I am in INS mode and putting the TVV on a point on the ground and tapping TDC action creates a target diamond w/o issue. I just can't slew the diamond around, neither with my X56 ministick axis, nor with the keyboard. Aforementioned axis work w/o issue in the TGP / DMT etc., though, so I must be doing something wrong. What would that be?
  16. Nope, no change for me
  17. Which is: - an advertisement - probably lab-tested - highly dependent on mounting platform
  18. This is so weird a bug - my buddy and me play MP pretty much every second day now, and I never ever had one CTD in the F-14 so far. Here's to hoping they manage to nail it down.
  19. That's the thing: you can only enter data on the scratchpad when the AAP is set to OTHER. In POSITION, STEER and WAYPT it is read only, isn't it? ***EDIT*** after rereading the section in the manual for like the 3rd time: looks like you can only call up specific Waypoints / Mark Points to use on the STEER page when the STEER PT dial is set to MISSION or MARK, not FLT PLN. I kinda find that dumb if it was the case, since the flight plan is what I am interested in, but alas! :D
  20. Because it's no bug, but the correct setting. https://forums.eagle.ru/showthread.php?t=242533&highlight=efuz
  21. I think I bought the A-10 a year ago, never did much in it though. With the LITENING2 upcoming for the F-18 and the gfx overhaul on the horizon, I started to dig in though. So far I could answer all questions myself, but here is one that evades me: when I got the AAP dial to other, calling up the WP page and then searching for a waypoint by number or ID - is there a way to directly select that waypoint as steerpoint, or do I have to go through those sequentially with the switch / UFC rocker / HOTAS control?
  22. That link is dead, unfortunately - do you happen to know what the title was?
  23. Auto trim is an option to be used in the upcoming MAC, they are using DCS as a testbed. Don't use auto trim. https://forums.eagle.ru/showpost.php?p=3944526&postcount=16
  24. So, there is no UI that I am aware of to the open beta standalone server, nor is there any argument to set or withdraw to start it WITH aforementioned UI. Still, the options.lua is in the expected ..\Users\<username>\Saved Games\DCS.openbeta_server\Config\ folder - it is pretty empty by default, but it HAS the plugins entry - so what you can do is simply copypaste the Tacview options from your client. This is my whole options.lua for the standalone server now, TacView now runs without the 10 min delay w/o issue options = { ["graphics"] = { ["height"] = 600, ["visibRange"] = "High", ["width"] = 800, }, ["miscellaneous"] = { ["autologin"] = true, }, ["plugins"] = { ["Tacview"] = { ["tacviewBookmarkShortcut"] = 0, ["tacviewClientTelemetryPassword"] = "", ["tacviewCompressionLevel"] = 1, ["tacviewDataRecordingEnabled"] = true, ["tacviewDebugModeEnabled"] = false, ["tacviewHostTelemetryPassword"] = "", ["tacviewPlaybackDelay"] = 0, ["tacviewProfilingPeriod"] = 600, ["tacviewRealTimeTelemetryPort"] = "42674", ["tacviewRecordClientsSessionsEnabled"] = false, ["tacviewRemoteControlPassword"] = "", ["tacviewRemoteControlPort"] = "42675", ["tacviewTerrainExport"] = 0, }, }, }
  25. Probably, didn't have that information yet, though - will look into my server later today!
×
×
  • Create New...