rob10

Considering they got slapped by ED for what appeared to be a tease or hint, you're likely going to have to wait for the announcement rather than getting an announcement that an announcement is coming.

Unfortunately a long standing bug that as far as I can remember has never been fixed.

Would be great, but I'm pretty sure you're reading way too much into that. I don't doubt they'll add detail to edges, but ED has already said that PG (and other older maps) was built on a completely technology than that newer maps so they'd pretty much have to start from scratch to add the PG parts to the Iraq map. Or wait for the new "global" map at some point (likely in the longer term, if we're dreaming maybe the medium term) that will cover both areas.

There are none YET. ED has been adjusting the overall dots, but nothing headset specific has been released. The only reason it may look better in the Quest Pro is because it was changed globally and the current version happens to be OK for that headset. Which is exactly why they are working toward headset specific settings (because a global setting clearly doesn't work on all headsets).

Already been requested/discussed here:

Both those logs are still showing a bunch of mods in your saved games folder. I'd start looking there.

No, because they only contain NON-STANDARD stuff, not actual official and unaltered DCS files.

Reported and acknowledged in this thread:

Looks like you're getting zip file errors from your mod. The last hotfix mentions fixing that, but I'd start by uninstalling your mods to get going again anyway.

ED is working on making it headset dependent, but that is not implemented yet.

If one of you would post a track file it would be very helpful to see if this is something on your end or a widespread bug.

Test IR strobe 1.miz Yep, just tested it in a simple mission I made when I was trying it out. Note that it is now actually integrated into MOOSE, so as long as you're using a current version you can use: local IRGROUP = GROUP:FindByName("Ground-1") IRGROUP:NewIRMarker(true) I haven't been able to get them to turn off yet though. Mission is Syria and F-18. Row of infantry and tanks before and across the runway at WP 1 (note elevation at WP 1 isn't set to ground so if you WPDSG it will put it in the air).

As has been alluded to in previous posts, after the Hawk debacle ED stated that they would add a requirement that they get a copy of the source code so they can at least maintain modules at a functional level (I don't realistically see them taking over development ever, just too much involved to get up to speed) if something happened with the dev. Speculation is that the F-15 contract predated this clause (which is plausible due to loooonnnnggg development times for modules). I agree they should either make sure it continues to work (at least for a reasonable amount of time -- not sure I'd hold them to keeping it going for 20 years past developer folding) or refund it. But I don't see that they have a responsibility to take it beyond where it was at the point when you bought it. You're only guaranteed the state it's in when you bought it but one hopes it improves beyond that or the dev doesn't have a long future ahead of them.

They've said NO to planned updates and the likely reason (not stated) is there is no economic benefit for them to do so and they don't have a big team so they can't afford to.

Like Phantom711, I don't want to turn this into a how to AAR thread, but if you're getting pushed aside at the last minute you're probably getting above the wing level of tanker which can put you into significant turbulence off it.

Did you do a REPAIR after you set the exception? That file may still be quarantined if you haven't replaced it.

You might want to make your new pilot INVULNERABLE in the logbook. If you don't and you die in a mission that pilot is dead and gone.

If you chose the one 4 options up (with the LAU-117 rack) I'm guessing you'll get what you want. That option explicitly says LAU-88. You are choosing to load a single MAV-65D (same as the one on the LUA-117) on a triple capable rack. I can think of reasons why you would want to do that so that's why the option exists. The larger options aren't available on the LUA-88, but there is no reason you shouldn't be able to load a single MAV on it if that's what you choose (which is what you're doing).

Actually, while it's not readily apparent, this is currently what it does. If you cancel it will appear to start over because it restarts at 0 MB of XX MB. But if you look when you restart, the XX number will be smaller than if you started from scratch again. So if the whole update is 100 MB (I wish ) and you download 27 MB then cancel, when you restart it will be 0 MB of 73 MB (instead of the 0 of 100 that it would have shown on 1st try).

That's because DCS itself has NVidia stuff embedded into it for DLSS. You might not be able to use it with AMD graphics card, but I presume there is some sort of requirement to have that splash screen in the licensing agreement for it.

And see if either of these threads help. 1st one may help with the not reversing, 2nd was someone with a similar problem.

Have you tried clearing the calibration on you WH? Try doing that in the Windows game controller. I know way back when it was always recommended to use the TM software to calibrate it and if you used the Windows tools you could mess things up. IIRC this is not an issue anymore, but worth clearing the calibration and redoing it one way or the other.

As an FYI, pretty sure that Nineline (or at least someone official from ED) has said at this point that ED does not have the F-15 source code. Rest of your post is completely valid points, just wanted to mention this.

Actually the OH-58 accidentally received an unfinished and partial update (which likely broke more than it fixed or added since it was not supposed to be included). Polychop has already posted this in a few places.

Check the Thrustmaster subforum in the PC Hardware and other devices/Inputs section. Pretty sure I've seen someone have this issue in past, but I can't remember what the final conclusion on it was.