rob10

Tracks are not meant as a true replay. They were designed as a debugging tool so they literally record inputs and "recreate" what occurred based on that. Because of that anything that's slightly out of sync (it's only recording every x seconds, so it could miss a tiny correction) or something relied on a randomly generated event etc can throw off the replay from happened the 1st time (random event may have different outcome). ED has said they may create a new system, but it will be need created from scratch and that's a long term goal so don't expect to see it anytime soon.

Likely yes, but if that's a slightly older post ED has adjusted the controls on the F-16 in the last 6 months or a year so it may not apply anymore anyway.

You (mostly, there are a couple of exceptions) need to set up your fuze timings on the ground in the rearm/refuel menu (not any of the in-cockpit displays -- they're strictly for pilot reference/bomb computer use) because IRL you would have to physically change a dial on the bomb itself.

I think that's just a not super clear explanation in the manual. A lot of (digital) stopwatches behave exactly the way the Hornet one does. It "pauses" the display of the timer, but the timer continues in the background. In the case of a stopwatch it's so you can get a lap time while till continuing to time. I'm sure there are use cases in the Hornet where both to have it truly stop or just pause the display make more sense. The current behaviour doesn't surprise me at all.

That is not the 1st thing everyone does. That's why it's always the 1st thing that is going be suggested to anyone with this problem. As has been proven on the forums it is quite often (definitely not always) the reason for the issue, and in those cases people HAD NOT checked that their AV was or was not the problem)

That appears to be one larger monitor behind the pair of them, rather than actual sized video screens for each if that's what you're looking for.

IIRC you can adjust the time it will send the pressed signal in SimAppPro to something longer and it should let you change the heading. But, as the others have said, it's not going to be a good experience because you'll be turning forever to get not very far. Better to have it on a switch where you can hold it and it will allow you to type what you want on the UFC after a few seconds.

IMO, leave them un-tuned and symmetrical. Yes, maybe it's hard initially, but you'll figure out how to tame it quickly. And once you have tamed it, you have symmetrical controls which likely makes things easier down the road. But that's just my opinion. If you want to mess with it, in SP you can go in and out of the bindings and play with it at will, and that's likely best way to tweak it. Try to only tweak one axis at a time so you can see what it does. I would start by adding a little curvature to flatten the centre of the response. Then increase if you still don't like it. Again personal opinion, but I would avoid deadzone if at all possible as that tends to make things jerky. To tame things down while AARing, try gripping your stick close to the base. That will tend to dampen your movements for while you're doing that while still giving you full responsiveness the rest of the time.

Sorry, but you're wrong on your assumptions. There are many posts here of people that lost authorization for modules after an update due to their AV solution deciding it suddenly didn't like a file (often a .dll).

System RAM: 15315 MB, Pagefile: 11776 MB You're playing with only bare minimum RAM requirement. I'd bump your pagefile to a fixed min/max of 32,768GB and make sure it's on a fast drive (not a HDD).

It could be as simple as adding a comma on a line. Even that would put ED in legal peril if they did it without RB's permission, and there doesn't seem to be any goodwill at all between the two companies so your chances of seeing that happen are nil.

It's not worth "bumping" this thread. ED literally can do nothing directly with the F-15 stuff until this is settled. Even the radar issue they "fixed" was a work around outside the F-15 code. The chances of them spending time to come up with a work around to add one entry to the RWR file are nil.

90+% of the time this is due to your anti-virus blocking files. You may get it to work once after a repair but it will keep coming back if it's antivirus related. Currently you've given no details on "what" is happening and/or any steps you might have tried to fix it. There are a few other things it could be, but suggestions at this point would be purely guesses without more info.

Won't argue that the odds of Razbam doing it are going down every day, but technically it's not "dead" yet (since the legalities haven't been settled one way or another) so it's not possible for someone else to step in yet. No idea what contracts exist in this situation, but likely if ED allowed someone else to start officially working on it Razbam would have a claim against them currently (even if RB have no intention of doing it anymore). Short version is that anything related to RB is at a minimum frozen currently until they settle or officially breakup.

Presume you meant added them to antivirus exclusion.

Thanks for coming back with your solution to the problem!

It might remove some bluriness, but the symbology is still too chunky/thick even when barely visible.

It's really helpful if you provide a new .log file after you make changes. It's possible you have multiple issues and after fixing the 1st issue the new one may show up in a new log.

Try updating or re-installing your Windows Visual C++ Redistributables. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 That's what it seems to be choking on.

I wouldn't say it's blurry, so much as the letters have almost become bolded which makes them harder to read/ugly and agree that this changed just as of last update (wasn't like this previously, so different issue to the Dec '23 one for users currently starting to experience it). This seemed to be a fix for a problem some other users were having and I assume at higher resolution it looks better, but it's now degraded things for a different group of users. Seems like this needs to have options depending on resolution used.

It was added a couple of years ago, but never really announced and only gets mentioned occasionally, so I'd bet MOST people don't know about it.

You should be able to do a RIGHT click in binding for "close" and assign it to "off" to make it work (with "on" bound to "open").

ISSUE 2: you need to bind the MIP controls in you DCS bindings. Some may be automatically assigned (which is why some may work). ISSUE 3: not sure how this works in VR, but in 2D I would suggest making sure you select "WINWING" in your MONITORS selection in your SETTINGS/SYSTEM menu.

You haven't been around long based on your number of posts. After you've been here for a bit you'll realize how often MODS break things after DCS updates. Works fine before and breaks things (even seemingly unrelated things in some cases) after. Great example was the update where a number of different mod planes caused the supercarrier to not spawn when starting a mission (even if you didn't have the mod airplane in the mission). You would start a mission with say F-18 on the supercarrier and you would instantly plunge into the ocean and die because there was no carrier. Remove the mods and the carrier worked fine again.

See this for details on how to run a repair without running DCS. https://www.digitalcombatsimulator.com/en/support/faq/repair/