rob10
-
Posts
3375 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by rob10
-
-
Are you using McAfee? If so it may have quarantined a couple of the files so Steam can't find them and tries to redownload. Might need an exception in McAfee to get around this. If you're not using McAfee I'm maybe sending you down the wrong rabbit hole in which case I apologize
.
-
1
-
-
SLOW DOWN!
Seriously, if you're going too fast (especially when you engage it) your front wheel will start to slip and you won't turn (or may turn odd directions even though the wheel is turned). Even more noticeable on ground runways.
EDIT TO ADD: and too fast is not very fast at all (i.e. you don't need to be flying across the deck to be too fast)
-
2
-
-
11 hours ago, RedTail11 said:
Still happens to me all these years later. I've just been ignoring it for the last 2 years I've been playing but I'm at the point now I play a lot more F/A-18 and it's getting obnoxious. Happens no matter what whenever I advance the throttles past halfway, unless the MC is already lit from a previous throttle advance. Happens from cold start, hot start on the cat/runway, or already in the air. Tried the usual Google search but it looks like no one has an answer and all the threads on DCS/Reddit are old and dead.
Check your WINGS LOCKED, TRIM, FLAPS at 1/2 and SEAT ARMED. As Foka said, it should give you an indication in your left DDI. Only time I get this usually is when I forget to lock the wings (often when pushing throttle forward when hooking to the cat).
If it isn't one of these check post a track and someone will spot what you're missing.
-
12 hours ago, Ruthenican said:
I feel embarrassed, but I want to provide an update for anyone facing a similar problem. It turned out the issue wasn't with INS but with the alignment of HMCS facepalm. Once I corrected the HMCS alignment, everything worked fine. I didn't know about this feature before, and I hope sharing this can assist others who encounter it. Thanks to everyone for their assistance and responses.
No need to apologize. Thanks for coming back with the solution. If you had the issue the chances are that someone else will in the future and your post may well help them solve the issue.
-
What's weird to me is that restart doesn't fix the problem but shutting down does
. I am far from expert on Windows but my understanding is that restart should "clean up" windows more than a complete shut down (which is more like a suspend except that it powers the hardware down) these days.
-
May be completely unrelated to this, but any chance you are using McAfee anti-virus? It's been causing people issues with the latest update.
I don't use Steam, so I can't help with other suggestions if it's not that, but it's worth ruling out the easy fixes 1st.
-
1
-
-
Are you using an anti-virus? Since this seems like an issue that occurred on update I'd look there first. McAfee specifically has been causing a bunch of people issues with this update.
-
By the number of posts you have, you should know by now to start by typing "502" in the search box at the top right of the forum. That will give you lots of answers.
-
1
-
-
3 hours ago, Buzzf18e said:
I had to create an exception within McAfee to block the scanning of two files and it works now. However, this is how backdoor malware is created and it makes me quite nervous to do this.
As I said before, submit those files to McAfee so they can white list them, then you can remove the exception. Ball is in McAfee's court, not ED's.
Glad you got it working at least.
-
1
-
-
The only reports of people having this issue are those using McAfee. It's not ED's problem if McAfee is throwing a false positive or otherwise messing with it. You need tell McAfee so they can get it white listed or move to a different AV. There is no company out there that is going to change their programming strictly to avoid throwing a false positive with a limited number of AV programs, especially when it's the same AV programs that are consistently throwing false positives.
-
1
-
-
6 minutes ago, Buzzf18e said:
Lucky you Rudel! However, I do not shut off my anti-virus for whatever app, it worked before this update but now doesn't. I'm not going to allow a backdoor entry for folks wishing to infect others with any malware, ED this has to be fixed!
What anti-virus are you using? The vast majority of them have no problem with DCS currently. A limited few (this time McAfee, typically it and Kapersky, Eset, Avira) regularly throw FALSE positives. It's not up to ED to make sure they aren't throwing FALSE POSITIVES. If it is your anti-virus that's causing the problem, you'll have to send the "offending" file to them to check and have whitelist it.
-
1
-
-
Typically that means that your DCS is having problems contacting the ED servers. Can you use any other aircraft? The other issue some people are having with the last update is their anti-virus (mainly McAffee this time) flagging parts of DCS with a false positive.
-
1
-
-
14 minutes ago, 2circle said:
Thanks guys - I'll check it out. I guess my main question is how to force a flag off that was set to true, then allow me to subsequently set it as true again. Basically to go back and forth with the flags so I can better control my close escort.
Switched Condition trigger should work for flag. Above advice is good for what the flag should control.
-
1
-
-
Are you using an anti-virus program? McAfee seems to be causing issues with the latest update.
-
1 hour ago, zephi said:
So my friend did a slow repair all night, without uninstalling the mods (since he went offline before you flappie replied) and it worked!! seems at least in this case, removing the mods weren't necessary
Any mods that weren't in the Saved Games folder would have been automatically removed by the repair, so it could well have been a mod problem.
-
1
-
-
From lots of prior posts here, some AV options (espescially Kapersky, ESET, AVIRA and to a lesser degree McAfee) have issues with false positives with DCS (and presumably other programs). And have false positive problems consistently. IMHO if an AV is throwing that many false positives I'd move on to another one, because at some point it becomes like crying wolf and you're going to ignore an actual problem because you've had so many false positives. But that's just my opinion.
-
20 hours ago, draconus said:
The guy is trying to ask about the green parts (see below). It is indeed unclear if they are always low detail - and if not - which part of the map includes which one, assuming the whole map includes them both.
I understand that, but to me it's pretty clear that only the red, blue and black areas are high res (no matter how you buy it) and the other areas, as Hiob said are similar to the edges of other maps (so lower detail/resolution). Even when they talk about buying the whole map, they refer to getting the 3 high res areas.
-
2
-
-
8 hours ago, RegaeRevaeb said:
And I was just talking about getting access to high-resolution parts of the whole map remaining after someone has bought the three available piece maps. Hopefully that clarifies things.
The 3 pieces ARE the high resolution parts of the map. You get the same 3 pieces in high resolution if you buy them separately or the whole thing. You get the low(er) resolution for the rest of the area indicated as being part of the map whether you buy the whole thing or the three pieces or one or two pieces. If you only buy one or two pieces, the "high res" area's that you haven't bought are also in low res.
-
1
-
-
1 hour ago, SpiffnZ said:
Hi All
Is this issue still unresolved? I have just updated to 9.2.3.51704 as DCS was crashing at startup if VR was being used, & it still crashes out at the 15yrs of DCS screen.
Thanks
Sorry, but did you bother to read the post before yours? That might give you a good hint as to the status.
-
Are you in VR and using Oculus software at all? Likely this is the cause. Win 11 seems to be at least partly a common denominator (not completely clear since this appears to affect some people, but not all).
-
Your HUD is indicating what direction your nose is facing. The DIAMOND you are pointing at in the HSI page is the GROUND TRACK (i.e. what direction you are actually moving in relation to ground). It's not always intuitive, but because the BOAT is moving, so are you (even though you are parked on deck with wheel brakes/chocks). If you look at about 205 deg on the HSI you'll see a line on the compass rose. That is own ship (i.e. your plane) heading indicator (i.e. where your nose is pointing, rather than what direction you are actually moving).
You'll also see that disconnect if you're in the air and have a significant side wind. Your nose will face one direction, but the diamond on the HSI will be slightly off because it's showing where you are actually travelling since the wind is pushing you sideways. This shows up more on the boat because you are at nearly 90 degrees difference.
On the ground your nose and what direction you are moving will be the same (or nearly so), so they will match up. Notice the line on the outside of the compass rose in this case matches up with the diamond.
-
2 hours ago, j0nx said:
Why are we still dealing with this a month later? Why hasn't this been fixed yet?
It's been fixed for a while, but they have been testing to make sure that the fix for this doesn't break other things. It was supposed to come out last week but last minute issues (likely unrelated to this fix) had to be fixed.
And, while I don't understand all the details, I'm pretty sure it's safe to say that this wasn't just a fix that required changing a "1" to a "2" somewhere in the code so not a simple hotfix option.
-
And it would be worth posting your mission so someone else can see if they are having the same issue and why.
IIRC somebody else was having issues with things moving like that (static objects in that case I believe) on the Sinai map. Can't remember what the solution was, but maybe take a look in the Sinai sub-forum.
-
In part, a "once" condition trigger likely does some of this - i.e. stops checking after the condition has been met once. And "switched condition" would only be checking for the overarching condition before checking all the conditions within the trigger (which is generally doing what you want).
Going further with your suggestion is an interesting theory. My guess is that you would probably net out no better off simply because you're adding another layer of checks (to see if the flag is met and you should check all the other conditions) and it's going to have to continue happening while you ARE actively checking the other conditions to monitor when the flag turns off again (so more checks during the most intensive part of processing).
DLSS "update"
in PC Hardware and Related Software
Posted
Likely because 3.5 > 3.5.1 likely didn't require a huge amount of testing whereas 3.5 > 3.7 would need a bunch of testing. ED have said they will update it eventually, but that it would require testing to make sure it didn't break anything. And I'm presuming from the tiny bit I've read that it will require some additional behind the scenes changes to take full advantage of the new stuff 3.7 and beyond will bring.