_SteelFalcon_

Joke‘s on you, I eject prematurely when the rwr starts screaming at me

I tested it again with different settings and once on CAUC and once on Syria as i did originally for the tandem bug report interestingly, i was not able to reproduce the issue on CAUC. but on Syria, out of 4 JSOW, 1 falls 5-7nm short, 1 falls juuuuust shy and 2 hit reliably. i did test both tandem options, as well as single drops. see tracks attached JSOW_single.trk JSOW_tandem_line.trk JSOW_tandem_parallel.trk JSOW_tandem_line_Syria.trk JSOW_tandem_parallel_Syria.trk JSOW_single_syria.trk

here's a little track. it does dim somewhat, but not very noticeable. it's still either blinding bright at night or completely off. but from the hue around the text, it is visible that some dimming is happening, although not very useful. rwr_panel_dim.trk

Same observation here too.

what does that have to do with VIP/VRP?

This.

Iff in actually does function, long press sends spi over link16 to your flight.

Track?

You can use scenery buildings too. I use the pod in SP mode and pick a building to align them

as the title says

server-20230129-192334.trkserver-20230129-192650.trk. Seems to be working as intended. at least i didnt get any launch warning until the missiles from @Moonshine really went pitbull STT gives a spike but no missile warning until she's pitbull (test with the hornet). DTT does not trigger any warning until the missile really is pitbull. looks fine to me

Is the tanker on a specific tacan? If you change the tanker tacan freq. does D/L come back maybe?

For rolex you could use the delta TOS on the time page.

that i understand, but i do not understand getting an RWR tone from a fighter jet while sitting in a hangar or being all the way across the map, just because another friendly is in his range and being targeted.

the ALSA ACC document should have you covered, page 21/22

no, it "only" takes into account the currently selected STP, distance to it, your speed and the desired Time over Steerpoint, according to the -34

Interesting, but still strange that it‘s an issue.

Sounds like it‘s an issue if local and zulu are on different dates then?

Why track replay? Everything you need to see is on that screenshot… i have an unrealisticly high time to bingo compared to my fuel flow and total fuel load. With a fuel load of 8400lbs and a burn of 12300lbs per hour, it doesnt take a track replay to realize a time to BINGO (2000lbs) of almost 2h just cannot be correct…

the problem seems to be the TGP. if you drop JDAMs on a waypoint (that you place in the ME DIRECTLY on a tank, ground level) it hits. but if you use the pod, area track on the waypoint without slewing the pod at all, it misses by quite a bit, despite the target being in the exact same place. Even worse if you CZ the pod before the drop. and same goes for MK 84. if you CCRP on the steerpoint without the pod, it drops within 5m of the target. if you use the pod to designate the target, it misses by quite a bit.

Can you post the miz that you use for the tests? I‘d like to have a go at it.

One could argue that every bug is a wishlist item since we „wish“ for it to be fixed…

i'm seeing the same weird stuff...

how's that a "whishlist" thing now?

It seems that in DCS, the time displayed in the DED CRUS EDR subpage is calculated from the Opt Mach speed, instead of the current throttle setting. According to the -34 (page 1-328), the time should be dependent on the current consumption rate (fuel flow) and the current altitude, not the Opt Mach. I mean, it is impossible to have a time to bingo (2000lbs) of 1:55:42 with a fuel load of total 8400lbs and a fuel flow of 12300lbs per hour Some part of the modeling seems to be correct tho, as the speed in which the timer ticks down is dependent on throttle and altitude. but the base time value should not be calculated with the Opt MACH, but instead the current fuel flow. The caret in the HUD should show OPT MACH, but the time should be calculated from the current consumption, not OPT MACH.