rob10
-
Posts
3375 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by rob10
-
-
If you posted the mission so others could look at it would be very helpful.
-
The "B" instead of "K" is a longstanding issue due to the way certain aircraft are labelled and should have no impact on using it as a tanker.
I just set up a mission in Caucaus map using the settings you showed in your pic above and I had no problem getting contact with tanker and everything was english. Remove any mods you have installed and try again. If that doesn't work post a track and/or the mission here and we can see if the issue shows up for others.
-
39 minutes ago, majorandme said:
Did it work for you? This does not fix the problem
That was valid advice when it was posted (and up until last week sometime) because at the time the release version was V62 and the problem version (V63) was only a preview version. Since last week V63 is now the release version so doing this will no longer solve the problem.
-
1 hour ago, sylkhan said:
Coming from a true flight simulator it's always funny to see these arcadish items from Flanker
It's more cheating view and doesn't fit the simulator philosophy
If you want DCS to get that hardcore I hope you're willingto pay more like $1,000 - $2,000 per module for it because people that want it that hardcore are a small minority in DCS and # of users will dictate pricing. I say this a someone who turns off enemy unit display on F10 (when I use it), but I have no problem with people using this however they want. As others have said, if you're a MP server owner you can turn it off. Why the next guy shouldn't be able to have it turned on in his server if he wants is beyond me.
-
3
-
-
In the campaign mission selection list when you're deciding what to fly there is an option there to SKIP mission rather than fly next one. It's in the selection menu, not within the mission itself.
-
Are you in VR and have Oculus software on your computer? That's very likely the cause of your crash. There are a bunch of threads with details regarding that issue currently.
-
2
-
-
2 hours ago, Focha said:
I am sorry for the .track not being sent. I know it surely helps but it takes time I barely have (I don't work for ED).
Close mission, on debrief screen save track, attach file here. Virtually no time required. If it occurs well into a mission resulting in a big track file, yes that's a challenge.
The problem is that there are massive numbers of "bug" posts here that turn out to be user error, and without a track that can often show that very quickly, ED would have to flail around trying multiple things to recreate something that might not be recreateable. I get you don't work for ED (neither do I), but if you want them to look at a problem, you have to show them that there is a problem (especially when you're the only one currently reporting it).
-
2 hours ago, Mailman76 said:
dcs.log 16.98 kB · 0 downloads
I'm also having issues with the game crashing at splash screen. Everything was running fine for a day or 2 then I started having issues. I'm currently running v62 on
Had you done the steps to prevent updating? Having PTC off only worked until a few days ago when V63 was automatically pushed as their release version, so if you hadn't already taken active steps (beyond not opting into PTC) to prevent updating you're likely on V63 and have it's issues now.
-
36 minutes ago, Michi.G85 said:
Hm, I´m on v62, PTC is off but it still crashes (non-Steam). Any suggestions how to fix this issue?
Had you done the steps to prevent updating? Having PTC off only worked until a few days ago when V63 was pushed as their release version, so if you hadn't already taken active steps (beyond not opting into PTC) to prevent updating you're likely on V63 and have it's issues now.
-
1
-
-
Just to cover all the bases, have you tried renaming you Saved Games folder to something else and letting DCS recreate it (i.e. run DCS after you rename it)? That might get around it if there is a file in there causing the problem.
-
1
-
-
That's currently a ST VR only bug. Has been reported, but like any ST only bugs it may or may not get fixed soon (likely depending how easy it is to fix) since ST is nearing the end of it's life.
-
2
-
-
8 minutes ago, silverdevil said:
hi rob. what i meant was that roll back to the version that worked. and disable auto-updates which i guessed in a sense was PTC (forcing a test version on everyone). i do not have VR so i am only going by what i have read on the forums.
We're both in the same boat of trying to help without having the actual issue
. But from what I see you CAN'T roll back anymore (you could when it was just preview version only being released to PTC) so if you've already been hit by the automatic update by the release (non PTC) version your options are limited. That changed in the last couple of days. Before that the problem version was only being pushed to PTC and if you unchecked that it would downgrade to V62 and solve the problem.
-
1 hour ago, silverdevil said:
have you performed the roll back to v62. this is the version that works. if you opt out of PTC you won't get an auto update.
Unless I'm misunderstanding (don't run VR so I don't have personal experience), but V63 is now rolling out as RELEASE version, so PTC has no impact on this anymore. And it sounds like release version of V62 is now automatically updating to release version of V63. I haven't seen any confirmed way to roll back mentioned (one person mentioned they has seen an unofficial version of V62 floating around, but that could be a risky download.
-
8 hours ago, markom said:
I could be wrong, but isn't JDAM alignment just making sure they're on for 90 seconds?
Yes, but what I was thinking was what the OP discovered: if the PLANE isn't aligned properly that can throw off proper targeting.
-
1
-
-
Do you have Occulus software installed on your computer? If so look for the threads on that. Update today is not DCS friendly.
-
I can also say that I have no problem hitting even small targets like vehicles with JDAMS on MP servers. If it was a core DCS problem that all TOO JDAM on MP servers have been off by 100 m for over a year there would be a lot more complaints on the forums. You really need to post a short track and maybe someone will spot what you're doing wrong.
It really seems like you're used to doing hot starts in SP (which would start aligned) and aren't doing a proper alignment or something in cold start in MP, but without a track to see what's going on it's literally throwing darts with a blindfold on hoping to hit a correct answer by luck.
-
1
-
-
The topic has been discussed to death in the forums. Short version is that while ED likely agrees, it's not something they are able to make happen short term. There was a 3rd party looked at doing something formal on it, but they didn't end up going forward with it which suggests it's not that easy to do within the confines of how ED works/has to function (i.e. laws, information availability etc). Modders have a bit more leeway.
Definitely agree that Skynet is awesome!
-
Try turning FSR off. Upscaling using DLSS often gives some of what you're describing so I assume that FSR does too.
-
-
Are you using VR? Do you have Occulus software installed? If so the update for it today prevents DCS from launching (even if you try and launch in 2D). See other threads in VR problems.
-
3 hours ago, les said:
I should have also said the ticket reply suggested I go off beta updates for the oculus but im not using the PTC so cant really
do anything here!
Going off PTC wouldn't have helped you with this one at this point (it did up until today) since the DCS unfriendly version is now their release version.
-
From other posts it looks like UNCHECKING PTC is not longer going to solve the issue. The 0.64 version is now the full release version. And I think just having it installed on your computer is going to mess with DCS starting (VR usage or not).
I get the hate for Meta over this, but really it's hard to put blame somewhere specific with this one. Beta can't test every possible game, so breaking DCS (since it seems to work with pretty much everything else) it's hard to say they should have "fixed" it. On the other side, DCS can't be expected to test against every hardware combo (and every version of firmware/software) others are going to put out. Yes, they had some warning that this was coming and they appear to be working on it, but as a percentage of total user base how many will this effect? It's a lot easier to disrupt development (which pushing a hotfix would do) if it's effecting everyone rather than a small %. Assuming they even have a fix ready yet, it's likely not a tiny change so it's going to take a bunch of testing before they can push it and separating this fix out from whatever else they've changed is probably a nightmare.
I do hope that ED does make this a priority though, since it's completely breaks things for those who are using Occulus.
-
1
-
-
I used exactly what Exorcet suggested recently to simulate a delayed secondary explosion from a hit on a bomb making factory (initial explosion from dropped bomb, then slightly delayed and bigger secondary explosion to simulate the explosives in the factory going off). Worked really well.
-
1
-
-
9 hours ago, Elphaba said:
. No reason except artificial limitations.
Completely agree this would be AWESOME to have available, but not sure I agree with the above statement. I have no idea how the background programming works, but as cfrag said, on the mission editor side I think it's a bit cobbled together rather than well planned out. It wouldn't surprise me if they can't easily allow this because of the way units are "grouped". There's a bunch of other stuff that is only changeable for the whole group, so seems like that might be the level at which it computes things (likely to save resources). So while I'm sure it's possible to do this, I don't think it's necessarily a quick and easy change to make.
-
1
-
DCS Crash after initial load
in Game Crash
Posted
That solution no longer works since last week when Meta pushed V63 as the release version. Look in the other threads and there are some other work arounds until ED pushes the fix from their end.