

cw4ogden
Members-
Posts
339 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by cw4ogden
-
Randomly becoming blind while flying at night. Can't see instruments.
cw4ogden replied to audiman's topic in 2D Video Bugs
I've had the problem I described for quite some time. Yours just sounds like the same thing only it's not as a result of switching views. I'm trying to wrack my brain for things I tried. I am in VR too, but it sounds like you are not? That would rule out all the VR settings right out of the gate. I fly A LOT of night. When I run my server it's called "Cold, Dark and Miserable", so It's kind of my thing. 99% of DCS online is daytime flights. This is under the radar because so few people are seeing it is my guess.- 63 replies
-
- 2
-
-
- graphics settings
- visual effects
-
(and 4 more)
Tagged with:
-
Randomly becoming blind while flying at night. Can't see instruments.
cw4ogden replied to audiman's topic in 2D Video Bugs
Just curious if this happens to you after looking at the F-10 map or external view? I get the very dark cockpit at night pretty frequently and it's always after cycling thru external views or looking at the map. If this is your issue, for me it usually self corrects in 5 to 10 seconds, or you can toggle external view / cockpit view a couple of times and it resets to cockpit gamma levels.- 63 replies
-
- 1
-
-
- graphics settings
- visual effects
-
(and 4 more)
Tagged with:
-
Yes. You essentially race the dust cloud forming behind you, and once you're ready to land, you transition to a rapid deceleration, trying to simultaneously bring airspeed and altitude to zero or near zero, before being engulfed by the dust or sand etc. One crewmember calls the dust cloud's location, the other aft wheel height, sometimes it's just one crewmember doing both. Nothing else requires the kind of split second timing dust landings do or did, prior to the F model. I hear the F model can do it for you, but in the D model and prior, it's akin to a carrier landing in terms or sheer sketchiness. It's a controlled crash. It happens as fast as you can read this: "Aft gear is off, 50, dust cloud forming at the ramp, aft gear is off 25, dust cloud mid cabin, aft gear is off 10 feet, dust cloud cabin door , off 5,4, 3,2,1, contact" the last two to three seconds are often flown totally blind, just relying on everything looking good at the moment you get swallowed. The danger being spatial disorientation, once you are engulfed in the dust, you damn well better be on the ground or very near with no side drift, because even though you have an artificial horizon, it can't show you drift. You can be straight and level and sliding 15 mph sideways, with no real indication. That's how accidents usually play out, botched approach resulting in a completely browned out pilot who can't see the sideward drifting which becomes a rollover accident on touchdown. Here's a few good videos. Video number 1 is a textbook dust landing. It's just about perfect in terms of getting down with the least amount of forward motion before the dust swallows them. Versus in number two, you can see the bird is enveloped for up to three seconds before they actually touch the ground. Not sharpshooting the pilot, as they could probably see thru that level of dust, to some degree with the NVGs. But that's the difference between what I'd call a good dust landing and a bad one. It's subtle, but notice on the day video, the back wheels contact BEFORE being engulfed. The second video, not so much. The third is a pilot's perspective but it's an F model, so likely this is an entirely different approach profile flown with and relying on hover symbology. And it's of course daytime. The approach is much slower, very controlled feeling, and provided mostly to illustrate what the inside of the dust cloud looks like. Cheers!
-
As another former 47 guy, I’ll confirm pinnacle / ridgeline landings look way cooler than they are hard, or require skill and or a great cyclic touch. On the other hand, getting that huge SOB down in the sand or dust at night with NVGs, that was incredibly close to the edge flying. Don’t know many guys that NVG dust landings didn’t give them at least a bit of the heebie geebies. That’s how you knew you’d made it to the show, we’re in the club etc, when powers that be trusted you with 50 heroes in the back, going into the green void on a moonless night for God and country! NVG pilot in command is where the rubber meets the road in army aviation, everything else is some form of copilot.
-
cannot reproduce Engine issues when using MW-50(bug?)
cw4ogden replied to oncomms's topic in Bugs and Problems
Since then, I've gone out of my way to repeat it and nothing. Full mw50, emergency engine handle, low speeds high AOA just abusing it and nothing - it just hums right along. But yes, whatever it was I finally saw it, it had a sound associated with it, and no rhyme or reason why it should have quit. -
cannot reproduce Engine issues when using MW-50(bug?)
cw4ogden replied to oncomms's topic in Bugs and Problems
@oncomms @Hobel My apologies to you both, I was able to reproduce the bug. Sorry for being skeptical, but in the video it looks like engine mismanagement. My conditions were about 30 minutes into a mission, both temperatures around 100-110C, level flight. I engaged MW50, needle moves, started a clock figuring I had at least 3 to 10 minutes before anything would start to overheat. Engine made a sound I've never heard, loss of power followed by and subsequent total seizing of the engine. I'd guess it occurred within 30 to 40 seconds of what I'd consider "proper" mw50 use. No useable track file as I was 30 minutes into the mission. -
cannot reproduce Engine issues when using MW-50(bug?)
cw4ogden replied to oncomms's topic in Bugs and Problems
Ok I see the MW50 engage at your timestamp. Your temperatures are at the high end of normal when it engages. From there, they rapidly exceed the temp limits. Regarding the engine time limits, I've read up to 30min with mw50 and 3 for 3250 rpm without mw50, but I have not tested those. Either way, those time limits are dependent on keeping the temperatures in the proper ranges. Meaning 30 min of MW50 might be possible in less demanding situations, but throw in a sustained climb or high power, high AOA, low speed flight, and the 30 minute limit is superseded by the harder and faster temperature limit. There's a bit of a hierarchy to these limits: Time limits are softer limits, if you will. A 30 minute engine oil temperature limit would be designed to prevent sustained heat damage, reduce wear etc, but it is very very secondary to the keeping the oil temperature within its range. Oil temp is a hard limit, it has a gauge and a number, probably because it more important than the generalized time limitation. In summary, I think you are treating the 30 minute limitation like it drives the train, when in fact, its the other way around. You can get up to 30 minutes - IF you obey the other limits. Are you adjusting the thermostat or leaving it in the default position? -
cannot reproduce Engine issues when using MW-50(bug?)
cw4ogden replied to oncomms's topic in Bugs and Problems
Nothing I see looks like a bug. I fly the dora routinely, and it is one of the most reliable ww2 engines of the models we have. At about 19 minutes or so, when your engine dies, it's pretty much beyond they needle's range of measure hot. Did you attempt to maintain engine limitations? Specifically temperatures? The plane cools well in auto, but sometimes you need to tweak the thermostat a bit, in sustained climb, and definitely in the power range you are operating in. I have it mapped but I believe it's a knob under the gunsight. I'm Unable to see your cockpit switchology on youtube video, so a few things it could be: Can't verify you turned on the MW50 circuit breaker and the switch, but assuming you did. Also in the video, I never see the MW50 needle move. So maybe you were in a bird with no mw50? Going into mw50 with no mw50 onboard, or having it off will cook the engine. You should see the needle jump when you engage mw50. It's one of a dozen little things you need to check for, and to me that makes the ww2 genre fun. -
I've flown it online consistently for a week or so with no engine failures. I have not deliberately tried to make it fail, but I've yet to experience an engine failure through mismanagement etc. Seems to work fine if you obey the engine limits.
-
Indeed. My assumption was this was pretty much only used by the warbird folks. Vanilla spotting is not too far from realistic, in my opinion. But it’s a realism that could give a bit for gameplay. Or at the least, needs to be enforced equally across all resolutions.
-
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.
-
cannot repoduce and missing track file Salute no longer working
cw4ogden replied to markturner1960's topic in DCS: Supercarrier
@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.