rob10

DCS servers had a glitch and was reported as fixed at some time after you would have posted, so should be working properly again.

At first glance I'd bump your pagefile to 32GB (currently using 10 GB) and drop your preload radius (currently set at 100K). Those 2 things are probably limiting your memory.

If you're running into this issue since late November I doubt it's ED's servers at fault. The forums would be screaming if a large number of people were running into this. As Silverdevil said, it can happen on an occasional short term basis (i.e. on patch release) but not extended periods. I don't have much expertise in diagnosing that type of stuff, but I'd be looking at you internet provider and whether they are throttling DCS for some reason, or something with your anti-virus/firewall blocking things.

Do either of you have mods installed? Likely there is a conflict with one of them (at least one other user has reported exact same issue with this update and it was a mod conflict) so remove them and test again, then re-add until you find the culprit. Since there are very limited reports of this it's almost guaranteed a mod issue rather than a bug that ED needs to fix.

Here is the correct place to report it, but the 1st thing you're going to be asked is "do you have any mods installed? If so remove them and test again". That's what Draconus was trying to say. Very, very, very often when people have issues (especially after a DCS update) it can be traced back to mods, and sometimes mods that they forgot they had installed. Not at all unusual for a random DCS patch to suddenly cause a mod that had been working fine for a very long time to break or cause DCS to break. Just random luck when the update changes something the mod relied on.

First thought is EASY COMM'S is on in either mission or your settings. 2nd thought is that you're obviously using at least some MOD (you've got grey screens rather than green), so start with removing them.

1st thing to check is if WINDOWS is putting the USB port it's plugged into asleep. It's been known to change them back even if you had them set not to sleep. TIR doesn't pull a lot of power some it might be seeing the port as not in use and shutting it down for "energy savings".

If you click the three dots in the top right corner of the message (beside "Author") you can EDIT the message. There is no way to completely delete it.

I don't really fly the F-14, but have you tried turning the lights OFF and back ON? I think you need to flash them maybe?

If you don't like it, petition the server owners to set it that way. If they don't set it the way you want, don't fly those servers. Others may want to play the game differently to you or I and that's completely OK. There is no right or wrong regardless of what you might want to believe.

The ETA is definitely borked. Same speed whole way through and the time was consistently going UP rather than down as I downloaded more.

S-3 was updated to a new higher rez model so old ones liveries aren't going to work unless they are updated.

Razbam is the just the publisher of the SA map, the developer of this map is completely separate from Razbam. So it has continued on with development despite the current conflict between Razbam and ED. That's why it's still being updated and development on the other Razbam modules are frozen.

By "browse back and forth" you mean change between pages? I tried that and made sure I was off the one I was changing before I changed it.

You've probably hit your upload limit on the forums. Go to your PROFILE and somewhere in there it will allow you to delete previously uploaded files and gain back some space.

You can do it without exiting DCS, but my experience this weekend (I was messing with kneeboards trying to get stuff out of way the elastic on the leg kneeboard in game) you can't change a plane specific kneeboard while you're in flight.

Yes, you need to bind the buttons on the MFD's in DCS. Personally I think that's a better way to do it than using the SimAppPro profiles.

It's pretty clear they're working hard to push another patch before the end of the year, but until it's cleared for release the most you're going to get from ED is "we're pushing hard to release another patch but I have no further news until it passes QC".

Has this changed over time or does that not completely wipe the JDAM and make it a dud (i.e. it wipes all the programming and what not) and completely unusable? I know that was the case when the F-18 came out, but that might have changed since.

To expand on what Tholozor said, these are planes made by competing companies for different military branches. This is not a choice of ED deciding to make it different for a different aircraft just for variety. They operate completely differently in the real world and that's why they are so different in DCS. I find I stick to one aircraft because the whole workflow in the F-16 is sooooo different to the F-18. In the real world that has very little impact because you're not going to jump back and forth so there is no reason for them all to be the same. Different design philosophies by the manufacturers and likely the branch they are being designed/built for.

Have you tried a slow repair yet? Looks like there are a bunch of damaged/corrupted files in your DCS install by the errors at the end of the log.

The co-ordinates will automatically pre-populate in WP59 if the mission creator puts a Bullseye on the map in the mission. All you need to do is make sure SEQx is unboxed and you can scroll to any WP you want. If it's boxed you're limited to the whatever WP's are in the sequence. Just unbox it (it will go from BOXED SEQ 1 to UNBOXED SEQ 2 to BOXED SEQ 2 etc) and you can scroll down through the markpoints and WP 59 is the next one. You'll need to go through the SEQx options to get back to a boxed SEQ 1 if you want to only have mission WP's available to scroll through. There are always 60 WP's (0-59) and 9 Markpoints available. In every mission, but usually only a small number actually get assigned to anything. The others are there with no co-ordinates if you want to use them. BUT if you have SEQ1, SEQ2 or SEQ3 BOXED you can only access the WP's set for that SEQ. When SEQ is UNBOXED you can get to them all.

Post a track rather than a video. It's likely something simple that will show up on a track. You realize you really shouldn't need to touch vertical trim if you're >250 kts anyway?

As long at the mission maker has set a Bullseye in the game it will automatically populate it to WP59. So just scroll DOWN past the Markpoints to WP59 and assign that and you're good.

I would be surprised if it actually does anything in game currently. Can't say for sure, just my suspicion on it. There are a number of items like that where the control is modelled but the action isn't.