rob10

This is the most comprehensive list shared by a user that I've seen. Note that you need to be in c:\users\usename\saved games\dcs\kneeboard\F-16C_50\IMAGES for specifc aircraft (note IMAGES at the end) and the file need to be png format with .png lower case.

ED have said many times that in the case of REDFOR it's more an issue of developing what doesn't result in ED staff in jail in Russia than availability of info on them. Chizh (can't remember exact spelling, sorry) explicitly said this in the last day or two. They've also alluded to it being a smaller market (which will be tested with the Mig-29) so less profit potential which is also a key consideration when they only release a limited number of modules over a 2 or 3 year development span. And if you don't believe that, look at the what most people would think of British aircraft (Harrier, Eurofighter) and the fact that it's not British version of them created or in development, and Britain has much less draconian laws in that regard than Russia.

This. If they "bought back" the rights to the F-15E I suspect they'd be better off to start from scratch on a new version than try to figure out the old code and carrying on with it. Especially when they would have no one from the old team to help guide them (such as you might if you bought out a competitor in normal circumstances and majority or even some of the critical staff stayed on).

You have a lot of setting pretty high, so I'd start with cutting back on those if you're having performance issues. If you hover over the options they will show you how much hit you are taking. But if you're getting BSOD in game, that's much more likely a hardware or Windows problem than a DCS problem. And at the end you're getting a # C0000005 ACCESS_VIOLATION at 00007ffe076703a7 00:00000000 which is one that comes up but I haven't seen a specific fix for.

Something has changed in the last few updates. It used to be you could just put 0 ft and it would figure out from the digital maps in the system (or some other magical source, but at least that gave some sort of plausibility to how it was doing it ) what the proper ground level was and adjust for it. Now if you put in zero feet, it takes that literally as zero feet MSL and your point is off because it's looking underground.

And pay attention to the split where you need to put the zero. If they give you 8 digits you need to split them 4 and 4 and add a zero to the end of each of those.

It's not an official ED program, but DCS WebEditor does the 1st request.

Wags mentioned in Discord Q1/Q2 2025. So it's coming likely by summer with luck.

A: Russian has much different laws versus the west, so even making stuff up could get you jailed B: good luck actually proving that in a Russian court anyway (see A).

You really think that this money is going straight into ED's bank accounts never to be seen again? Do you not realize that (whatever the outcome) the money collected and any interest on that money will be accounted for in the settling of this issue? I would be very surprised if any money's collected aren't being put in trust at this point until it's solved. In the end the money may go to Razbam or if it's decided Razbam net owes ED then ED may get to keep it. If it comes out in Razbam's favour, then ED would be on the hook for lost sales if they didn't keep it up.

Unless you're running VR and don't care about the displays on the UFC etc, your are stuck running SimAppPro. IMO it's worth a little hit because having that info showing on the UFC (and lights on throttle synced) etc add so much. Enjoy your setup.

Already reported about 2 posts down:

I spent 15 minutes fast forwarding thru that track and not sure I ever got to where you had an issue, so see if you can reproduce it on a shorter track. My first question would be if you behind another aircraft or passing thru the wake of another aircraft because it sounds like a turbulence issue.

Try setting your pagefile to a fix MIN and MAX of 32 GB. For MP 32GB RAM is marginal and you're only showing 5 GBish of pagefile currently. And have you deleted your FXO and METASHADER2 folders? There are a lot of shader compiler errors in your log.

Give it a few flights and (unless you're an actual combat pilot doing it regularly IRL) you will by instinct lean the correct way to see around the seat. I don't see this an a particular issue. Not knowing exactly how far you've turned your head is a limitation since you don't have peripheral vision in TIR and flatscreen. Experience helps mitigate that.

To clarify this, in SEQ 2 you would enter WP 15 as 1st entry, WP 16 as 2nd entry, WP 17 as 3rd entry etc (as opposed to entering WP 1, WP 2, WP 3 again).

See the 3rd post in this thread. Stennis currently has no deck crew.

Not sure what plane that is (obviously not the Hornet) but I'm guessing it gives you that warning because left side probe is putting you dangerously close to the tail wing on the tanker. No idea if that's a bug or if that tanker is incompatible with that aircraft or if you need to only use the right basket with that combo (isn't possible to force that in DCS currently).

And clearly ED doesn't feel the loss of your purchase of the Strike Eagle outweighs the cost to them if they don't protect their IP currently. Maybe over time that calculation will change, but currently not.

Yes, but my speculation was that in order to get a low enough weight to meet that requirement the tradeoff might be a slower explosive. Faster doesn't necessarily mean more powerful, so you might be able to get BIGGER explosive charge from a SLOWER exploding material. But yes, this is hypothetical speculation on my part.

I think most of the audio files are encrypted at this point, so not sure there is an option for doing anything to/with it. While a long time ago it was a little over-zealous in firing that sound (i.e. when it really shouldn't have), I haven't heard it in a quite a while. Just practice a little more and it should go away on it's own (since you won't be triggering it).

The other option would be to use something like AutoHotKey (AHK) which sidesteps the IC issue (at least mostly, not sure if some servers might have an issue with it running) and have it press whatever key sequence you need to set up things as you like. I use it to set up radar and JHMCS reject in the F-18. May need a bit of playing around with delays to make it work consistently (some DCS keypresses seem to need to be held for a small amount of time (milliseconds) rather than just a straight press to register), but it's pretty light performance and does a good job. Also totally independent of DCS so you won't need to replace anything when DCS updates etc.

A track file example of a comparison of both these situations is going to get you a lot more traction than just posting that they are different.

Maybe, but it's probably not that simple. This is way over my head, but the explosive speed of the Aim-120 might be slower (no idea if they're using the same explosive, just playing devil's advocate) explosive to get a higher warhead power with less weight or something, so exploding at the same time/distance one might hit the aircraft, but the other might not push the fragments to the target fast enough to hit the target from the same distance. Just pointing out that (while I'm a fan) "common sense" doesn't always match up with reality.

SimAppPro can have an impact in FPS. IMO, especially if you aren't using the vibration function, you should do the following: In the file \SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua CHANGE AT LINE 19 to 0.3: winwing.interval=0.3 -- default is 0.03 Basically this changes how often SimAppPro communicates with DCS. This reduces these calls by a factor of 10 and reduces the load. Back in the early days of SimAppPro this had a bigger effect and WW eventually changed it to this (or similar) by default to reduce the impact. At 0.03 the impact is much less now, but still noticeable. NOTE that you'll need to make that file read only after you change it as SimAppPro will change it back every time you run it. I'd recommend setting it off read only before updating in case something changes in that file during an update, but that's probably not required most of the time.