Good. I had been working on a mission with the Harrier and noticed that my AI wing-men would immediately spawn behind me on the Tarawa, then proceed to take-off and crash into me. Also, they would crash into the sea on the side of the Tarawa when attempting to land. Really put a crimp into mission making with the Harrier.
Hoping the ME bugs were squashed. I will not update until they are.
Let me know which ones and I can take a look.
I risked it and updated to check. The AI default tasking bug appears to be fixed. The TACAN bug might be fixed too but I havenāt checked.
On the downside, the Hornetās Sidewinder boresight circle is missing from both the HUD and HMCS, so you have no idea whether your heater is locked onto a friend or enemy
Hahaha and of course the STEP function for JSOWS and JDAMS has gone AWOL. One game-breaking bug after another.
Not a bug, apparently just design change.
There is no STEP option if QTY is lower than 2. Go to JDAM(JSOW) DSPLY ā QTY and choose stations needed. For release from one station select only certain one.
Well thatās frustrating. Official JDAM and JSOW tutorials are outdated, and the design change was left to the end-users to figure out, with no official response from ED until about a day later after confused voices asked why the STEP function was hidingā¦
Welcome to Early Access. The Hornet dev team made the change but it didnt get passed down the line it was coming.
I mean, āNO STEPā is written all over the plane, I figure it was something that wasnāt supposed to be there to begin with.
I have a mental image of the dev teamās office just plastered full of sticky notes, and the one that says āChanged PGM STEP logicā fell off and ended up underneath someoneās desk.
I havenāt been following the changelogs for ever (just since the new year) but I had noticed a pattern that OB patches always tend to contain some easter-eggs, some sweet and some sour.
That said, once this change makes it to stable (and therefore removes the old method from play) I believe itās fair to expect the videos to be re-released.
Also, more thorough change logs would be greatly appreciated including more context on individual items. Just a thought for the suggestion box!
In the mean time, itās trial-and-error with our Open Beta / Early Access and I tend to watch the ED forums closely to see if anomalies I notice are reported. I am also trying to get more into the habit of making reports myself - Iāve started to feel guilty about griping and not contributing.
Anyone else having CTD in DCS with latest OB? Iāve tried with/without VR,different missions different aircraft,Does not seem to make a difference.About 20 min in,CTD
I think Iāll switch to Stable version to see if that solves it.
Nope, been running 2+ hour sessions the past couple nights with no issues.
Same here. Even figured out how to turn the frickinā laser back on.
Ok Guyās Thank You,I think it might be a GPU Driver issue.
Some of the recent Nvidia drivers have been a bit off for DCS. Iāve been weary to update. Going to wait a bit longer.
ThereĖs clearly a lot going on behind the scenes, in DCS.
The depth of the systems simulation just boggles the mind!
And it looks great tooā¦
That Tomcat campaign is pretty cool. It takes place in 1992. Iām already on third mission, on my second attempt the FPS dropped over target area from 80+ to single digits, during my first try it was OK, weird?