cw4ogden

I don't see how this could be exploited. The problem is some users, depending on hardware and settings, can't see <profanity>. Others can, when that difference is exaggerated - it leads to the single biggest lopsided advantage possible, surprise. With the mod, everyone can see everyone to some extent. Why do I care if someone can make the dots huge? A guy who could see me already, can see me from further away. Who cares? It's the opposite of fun, as DCS hobbyists we spend time an inordinate amount of time tweaking, eeking out every last FPS, battling away the shimmering associated with games from the 1990s. To then be forced to choose between decent graphics, or being relevant to the server, to the fight? Bad guy sees you at 10 miles, you see him at 5. That you can be worked around. Bad guy sees you at 10 miles, and you never see him, even under the most ideal conditions that's the current status quo. And for the WWII genre it's utterly game breaking.

For that and other reasons I now play on the other WW2 server.

Agree, that seems likely - however, I did it via that or similar post, and the move happened yesterday or the day before. it’s happened I think three times maybe in the last few months. I can’t say it’s the patch process with any sort of high certainty. Only that the only thing I did between playing last night, and having it reset to default, was patch DCS.

@Minhal Thanks to you both for the suggestions. I am on a two day old reinstall of windows 11. I left DCS alone and it worked post win 11 O.S. re-install. I Had to moved saved games, load a few key bindings, etc. all of which could be the culprit so really not looking for a deep dive. I was looking for hey it's the XYZ mod. I generally un-OVGME everything but not always. Only mod I'm running right now I think was clear glass, which also no longer appears to pass IC. Anyhow I was submitting a data point to the community, and hoping someone else had seen it, more than asking for detailed troubleshooting. P.S. the only thing that changed between last night and today though was the patch. None of the things I listed occurred between last night and this morning's revert to takeoff assistance 100% on every plane etc. I went to bed, it worked. I woke up, patched and that's the only thing that transpired between having my specials changed to what I assume are defaults. I'm going to run a full repair slow version and go from there. Thank again.

I appreciate the feedback, but what you're suggesting is spending a few hours to potentially save a few seconds / maybe a minute every update. And also to risk messing up a functioning DCS build. I know there are a bazillion things that could be causing this. I haven't done any troubleshooting, nor am I likely to. It's not worth the hassle. I was just hoping maybe someone had seen this and could point right to the cause.

Thanks for the reply. Why Yes! Yes, I do! Sorry I just found it funny asking a DCS player if they use mods or tools. Meaning, which third party, totally necessary to enjoy DCS piece of mod software could it be? It would take some narrowing down, there's SRS, TACVIEW the brilliant A-4 Skyahwk mod etc being my point. Yes I have mods and tools of a varying nature, as do most here. It's why I hate making any DCS bug report because you have to caveat it with 10 different things. Yes, this could be me for sure. Just curious if it was affecting anyone else.

Does anyone else's DCS Options - Special get reset every patch? Is there a way to prevent this? It seems lately I have to recheck every plane's Special tab because it's reset to default. Most annoying is takeoff assistance defaulting back to 100, but it's annoying on a few levels. Thanks all,

Any smart people want to hypothesize why mixed reality would kill my internet speeds? I’ve been bitching at my internet people for months, and turns out it wasn’t them at all. It sounds like some bull<profanity>, but it’s definitely mixed reality, and or combination of mixed reality and dcs. I get 24 mbs normally. Booting up DCS and mixed reality drops it to 1mbs or less, with unplayable pings. It doesn’t happen in the startup until the moment mixed reality launches. And it clears once I close mixed reality. Bluetooth is off to rule out interference. And lastly, every so often it boots just fine, no slowdown. My procedure to play DCS is now to reboot over and over while checking internet speed, until I get a lucky boot up. Thanks all.

@jchenry There is a load profile option. It may be called something slightly different. Upper right I think of control binding page. You may have to navigate to find the right folder, but you should be able to get defaults back or even saved profiles. They are device specific If I remember correctly, so stick is a file, throttle another.

@SparrowLT Night launch in the f-14 is triggered by Nav lights being turned on. Not via salute.

If you already use DLC (properly) disregard. F-14 has the DLC system which helps control the E bracket. If you're not using that to aid your E bracket your missing an important tool. It can be done without the DLC, but it takes some very precise throttle. DLC should be deployed once you are in gear down, flaps down landing configuration. you'll know you deployed it when you have one spoiler half way up on each wing. That half extended position is the normal position for landings. From there, the DLC thumbwheel should be bound to something you can use on your stick. The DLC thumbwheel then allows you to fully extend or fully retract those spoilers, allowing you flick control of E bracket. For example, E bracket is high or going high you extend DLC spoilers to add additional drag, vice versa when you get slow you pull them in. It's a quick fix to the E bracket you back up with throttle changes. Once you get it, tomcat becomes much easier to hold on AOA. As comment on this: "There is another problem at this state, the f14A’s engine would be highly susceptible to compressor stall and would stall every time when the e bracket is catchable making landing very, very difficult." That's why f-14 pilots were arguably the best of the best of the best - meaning you have Pilots, CARRIER pilots, F-14 carrier pilots. There are hierarchies both real and perceived in aviation. I think the f-14 and the harrier both fall into the more "real" category. Not a navy guy, but I've long heard historically both those airframes initially at east only took from a hand selected pool of aviators. In any carrier landing you are riding a very fine edge of the low speed envelope. Landing that large an aircraft on a carrier is an engineering marvel and it's gonna force tradeoffs. All that is to say my guess is it's hard, because it was hard in real life. Try it with the proper tools though and it's very doable, even single engine with combat damage.

@Shaman Ideally it's preferable to solve a problem without investing an hour into downloading a track and going thru every detail. Most problems are little user errors. Add in the fact track replays are sketchy at best, I was hoping we could find an easy fix. In your case, since you confirmed it's not the easy stuff, I just spent the hour, coupled with writing this, it turned into two. Here's what I found: Two of four replays I watched, you just fly into the ocean. Nothing you did, in fact, the first replay was exactly as you described. But that's why many aren't willing to review replays. It's difficult to get much more from a replay that a few questions can't solve. And they can bug out. Twenty minutes of my morning was watching replays that ultimately just crashed into the ocean, a 50% failure rate which is impressive in and of itself. Probably time compression related, but no useful data obtained from those. With all that said, I can find no significant user errors you made that would account for the needle indications. After watching your replay all the way to the deck, I took control on the 2nd of the four replays. I was curious if engaging the system later, i.e. closer to the boat or if having centered needles at the beginning would help. Neither did. Watching the one replay that worked, and flying out of another replay: Same needle right all the way to the deck indication. I did not bolter, but I suspect that is purely the luck of draw on the auto-throttle oscillation cycle. Next I checked a couple of youtube videos to see if maybe it was always like this. No. Many videos show it clearly holding centered needles right up until crossing the stern or so. Crazy wind? No. The wind is neither strong, nor far off from BRC. Your aircraft is in perfect trim. The only other things I want to check are, is it map related? Meaning just Marianas, or is it related to your .miz? Meaning do you get the same result in other missions, maps? Unless someone else sees a cause, this looks like a potential bug.

First thing I would check would be for gyro drift. In level, unaccelerating flight, you can look at your right knee area at the little line indicator with a round button next to it, it should be pointing straight up, or you can also look on your radar display - you are looking for a steady IM on the right middle. If it's flashing IM / MG (don't quote me on those) you need to press the little round button and align your compass card. From the screenshot it's not possible to see where your switchology is, but make sure datalink is set to the carrier, and the TACAN / Destination / AWL/PCD button should be on AWL/PCD. And the two AWL switches for HUD and VDI should be in ACL. Cheers,

Hitting very maneuverable targets is easier if you try to draw or pull a line of fire with your guns over the target, as opposed to firing when the enemy is in your pipper. Pull a burst thru his flight path, as opposed to trying to nail him in the gun sight.

Brakes on. Normally I remove the chocks, but he seems to do it with or without chocks in place. It's most egregious if the boat is turning or foul weather, but some other factor, possibly sea state or multiplayer desync maybe it can happen with the boat steaming straight ahead, in seemingly calm seas. Aside from being annoying, in the Su-33 for instance, it takes many iterations of going thru the F10 refuel menu to top off, I'm talking seven or eight times as he gives up consistently after the fifth "Hey what are you doing", prompting a need to go thru the menu again. Then on or two more times to get weapons on. In the F-14 on the Nimitz class, It's more an annoyance, but in the Su-33 it's a serious pain to loadout when he's being fickle.

Even with the carrier going straight, ground crew repeats "Hey!, what are you doing?". On the fifth iteration of his call, any refueling or rearming in progress stops. Ground crew should be less sensitive to whatever motion is causing him to panic, or at least not interrupt the rearming process. Happens with f-14 as well but not as easily reproduceable. Attached a track file but it appears corrupted or something.

Appears to affect both f-14 and f-18, after landing and refueling / rearming on super carrier. On the subsequent catapult launch, the flight control surfaces do not move during wipeout. Elevons move very slightly, no other normal control surfaces move in response. Flight controls work normally again once catapult shot is complete. Can provide track if more people are seeing this.

To you as well. My frustrations with third party apps aren't your fault. VAICOM existed because Jester 1.0 never got a revamp. The first attempt at making an AI RIO interface was a great effort, but it still has a couple of glaring shortcomings evidenced by the need for things like VAICOM and / or voice attack.

This is still a problem. Tend to agree with the original poster, the poor gyro is linked to low vacuum. As is, the plane would be on a red X, awaiting the crewchief to get his duct tape.

It was dead when I wrote this post. It was as dead for you as it was for me. Do you understand how the passage of time works? That things can happen, such as a community reviving it, doesn't change that this was accurate at the time I wrote it? I'm glad they've revived it for you Fanboi's, but its being saved from the grave doesn't make what I wrote inaccurate. It was dead. And news flash: It will likely die again. So much VAICOM water carrying here, when the point was the Jester menu should display, in VR, in the direction you are looking. Period. If I am focused anywhere besides straigt ahead, the system as it is, requires you to look away from whatever your focus is. It's most noticebable in formation flight, but it rears it's head in any situation your focus ISN'T straight forward. It's a simple request that was made more pertinent by VAICOMs Christ like death and reserrection. I'm glad it's working again for those who use it. For those who don't, a simple fix to the Jester code would make things easier on the rest of us.

It's dead to me. Glad to hear it was saved from the grave, but I'm still done with it. The functionality was always hit or miss, and it's just one more chance to be left high and dry following a patch.

I use time compression in lieu of being able to skip. Speed up to x4 or x8 while the text blurts out then back to real time.

With VIACOM dead, bumping this thread.

AI F-14s do this for me as well.

Also affected by this since most recent update with no workaround or fix discovered yet.