Jump to content

itn

Members
  • Posts

    123
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

  1. To both of the questions: No, not possible. As far as I know, not possible on the real jet either, but I might be wrong. Also, you didn't ask but no TACAN indications on the HUD either. So it's quite a bit different than, for example, the Hornet. I assume this is an Air Force / Navy difference, where the AF just hasn't had the need for it, at least not enough to spend resources to add them.
  2. Just to clarify, are you talking about a feature in the Mission Editor, such as an advanced waypoint action? Or did you refer to the same old scripting ways we're currently doing manually or with the excellent MANTIS/Skynet scripts? I could not see any new features like this in current DCS which is why I'm asking.
  3. Disregard, I misread your previous post. Your very first post seems correct in all aspects but the time it takes for GPS to sync (which we already discussed). At least with AI units (using an AI unit's STN as #2) It seems there are no ill effects with powering up GPS and MIDS LVT at the same time. Datalink apparently works the same and you see the #2 as blue on DL. Will test with humans later, but so far I can confirm the only ill effect is the GPS time off on DLNK page, and that one seems cosmetic.
  4. I’m not seeing it. Might test some more. Post a track? True, also why I mentioned the 2 minutes, as it’s longer than what was mentioned. Granted, I haven’t tested extensively what happens if you switch LVT on after 60 secs but before ”GPS” text is shown on TIME page.
  5. On my tests it takes two minutes from switching GPS on to seeing ”GPS SYSTEM” on TIME page. Where did it take you three minutes? Or did you perhaps look at the jet time, which will likely jump ahead a minute or so when GPS time is synced? Look at the mission time on F10 or info bar instead. I’m just curious if there are differences in different locations or such, and does it take longer in some conditions. I tested in Caucasus and Syria SP and MP. Sounds like as a consequence of switching MIDS LVT on too early, you have to fiddle with the DED pages, just like the workaround with the bug since previous patch? If you wait for the GPS time to sync first, you don’t have to do anything on the DED pages.
  6. You can use air-to-ground modes in NAV master mode.
  7. Delta TOS has been implemented and does work in Open Beta. @Nessie not sure what you mean with ME failing badly? I know it does work for a route where route start point is "Fix Time" (TOT) and rest is with speed. The calculated TOS is in waypoints. Haven't tried how it copes with having some additional steerpoints with Fix Times in the route.
  8. To add to this: If using metric throughout, the bug seems not to manifest. ME doesn’t allow fractional values for altitude (whole meters/feet only) and there’d be no unit conversion, so the issue just does not happen. Problem is with rounding and/or unit conversions.
  9. Not the same bug per description, even though similar and maybe same root cause. Maybe that ”minimum 30m AGL” in the other thread is not even considered a bug. My report is about a MSL waypoint having +30m added on group copy. Because ”0 AGL” is not possible, I have to enter target waypoint in MSL. Now if I copy the group, and happen to have AGL waypoints on route, the MSL waypoint gets +30m. And to be accurate, the one you linked was reported in January 2019.
  10. I believe this is the same or at least related to this: Using DCS 2.9.2.49940. When copying a group with AGL waypoints in it, MSL waypoints get additional 30m (~98ft) added to them. Steps to reproduce: 1. Add group with an AGL waypoint or two, and MSL waypoint. 2. Copy-paste the group in place, so the waypoints line up 3. See the copied group's last (MSL) waypoint, which is now 30 meters (~98 ft) higher than the original. In addition, even in the original group, editing the last waypoint from AGL to MSL is weird and it won't save the new altitude until you first switch it to MSL, then switch selected waypoint to other and back, then enter the new altitude (now in MSL). Without switching waypoint there and back, it won't allow you to change it. Attached is a sample miz where I copied the group. See Aerial-2's last waypoint. ME-AGL-MSL-add30m.miz
  11. Using current DCS OB 2.9.2.49940 Mission Editor displayed waypoint altitudes change when switching waypoints. It's frustrating error with hopefully a simple and quick fix. The values change by +-1 feet per my testing. I'm using imperial values and have not tested if similar problems exist when using metric in-game. A sample mission attached. In the mission I have two groups, with waypoints 0 and 1 set to same altitude. Aerial-1 has waypoints 0 and 1 both at 6000 feet Aerial-2 has waypoints 0 and 1 both at 300 feet Steps to reproduce: Select Aerial-1: Altitude is shown 6000 feet as set in the mission. Switch to waypoint 1: Altitude 6001 is shown Switch back to waypoint 0 and still 6001 is shown. Same thing with Aerial-2 at 300 feet, except for that group the errorenous value is 299 feet. Values in mission file are saved in meters. The values values in mission file do not change if you save the mission after switching and seeing the wrong altitude values displayed. I guess this is a simple rounding error in the display logic. The values in meters are 1828.8 (6000 ft) and 91.44 (300 feet). 1828.8 ~ 1829 which gives us 6000.656 ~ 6001 feet 91.44 ~ 91 which gives us 298.556 ~ 299 feet. It's a frustrating error when going over dozens of carefully set waypoints, and no matter how hard you check and fix the values, they always seem to change. ME-altitudes.miz
  12. Yeah, no. ED has changed their stance back and forth on having 2 or 4 HARMs. What we have is simply a 4 HARM capability and no additional "carry only" restrictions available. "Payload Restrictions" allows you to restrict per station, but no restrictions on firing them if you got them.
  13. Where? How? I see nothing in ME payloads/restrictions or in the "..." (Aircraft Additional Properties). Sure, you can disable HARMs altogether from those stations, but nothing about carry-only HARMs.
  14. With stored heading alignment it's the opposite: you must not enter coordinates (meaning you should not press ENTR at all on any of the three lines). Nevertheless it's good practice to check that the coordinates match to the position on Ctrl-Y infobar / F10 map. Again, not pressing ENTR, just checking visually.
×
×
  • Create New...