BlueAngel

So... There are no keys or commands to do this from a client aircraft? That's too bad. It's only eye candy, but adds some realism to screenshots. VRS Superbug adds the covers a few minutes after engine shutdown and the ladder is a simple key command.

I think the Tomcat should rush ED a bit. Or... it will be used as as cover for a developer slowdown. Let's just wait and see.

You clearly didn't watch the livestream. Why don't you go do it and listen carefully to the narrator. THAT'S where I got that from, Knock-Knock.

I can confirm this... two weeks later, this is still a thing. Since launch this radar has been one heck of an headache.

I wouldn't say "disappointing" but it sure is slow paced. After seeing Heatblur's promise to release all features from day one on the Tomcat (though their website states otherwise), I would say that's the proper way to work: Fully test the plane to exhaustion, THEN release it to testing. I think ED is changing their attitude towards this. The only problem is that they're doing this AFTER the plane was released to early access. That's why you feel disappointed.

I've seen some images where you can see the aircraft parked with engine, seat and antennae red covers and also the inbuilt pilot stairs deployed. Watching the Model Viewer software I can see the stairs animating, as well as the red covers placed. What are the keys and or conditions to make these work. Ground crew only places chokes and I can't seem to find specific joystick commands for these two events.

Nineline, the multiplayer issues I mention a few replies above began with Update 4 and arrived in Stable without correction. That's where we got that idea. But, good thing you released the hotfix 2 for the ME, on a sunday no less. But the Nevada and Normandy crashes are still a thing. If there's no fix until wednesday, won't you still release this version to Stable? If you do not, I stand corrected.

hiatus (hʌɪˈeɪtəs) - noun: hiatus; plural noun: hiatuses a pause or break in continuity in a sequence or activity.

An interesting initiative to ask what we think. My order of preference is: TPOD/ATFLIR (Mk.1 Eyeball just isn't enough in this game) Guided Bombs (what good would the above be without this?) JHMCS (Because AIM-9X needs this) HARM (Because AGM-122 in the Harrier is so crappy) Surface Radar (Because we need this in DCS for other aircraft too) But, I'm sure ED has their own priority list. Here's hoping they implement more significant AG updates because, for now, the AA focus is overwhelming.

If any fix is coming, it's not happening next week. So hang in there. Unless ED finally understand this two week hiatus isn't positive.

I had noticed this. There are items in the assets that seem to always get errors loading. And I've seen these errors for a long time now, since DCS 2.5 was launched at least. Working in a totally different field, if I find these errors in logs, it's always about wrong file location addresses. It's not finding the files because, for example, the file was renamed or relocated to another folder. This may be it. And, to be honest, it's a fairly simple process to edit the string or just move or rename the affected files. Doesn't sound like hard work. So I just may be wrong and this could a deeper issue. Like the loading of these files failing in the core programming. Either way, it's persistent and I agree this could be a cousa for some of the stutters.

Wait a second... Wasn't Razbam producing an A-6 Intruder too? Although they seem to be keen on dispersing in multiple projects, placing others down the list, I'm pretty sure I saw something about an Intruder.

I believe the countdown will be for the world reveal through a livestream. The release date for EA may be announced in that stream, though.

This next we will see how the Eagle Dynamics Stable/Open Beta logic will FAIL. This week's two updates introduced severe issues: Mission Editor crashes to desktop. Nevada/Normandy crashes to desktop. Persian Gulf may also CTD. If you are adamant to keep your two week model, not updating DCS outside your planned windows, you'll transfer these severe errors to Stable. And there's no reason why you should do this, whatsoever. Stable is WORKING right now. Don't ruin it, just update Open Beta this week again and THEN transfer the version to stable. It's the reasonable thing to do!

I'm not really against your model. Again, it's very sound in this industry and it works flawlessly with other software projects. Anyone would have to agree, however, that, as it is, it's somewhat a waste of resourses to have two facsimile versions with a two week delay. If Open Beta was to be a test platform as stated, how come multiplayer bugs and other issues still get into Stable? Worse, was it really a good idea to introduce these MP bugs from recent updates coming from OB, when stable was, well, stable? People were complaining for a long time prior to merging. They still passed. In my case I have severe rubberband lag and crashes to menu from incomprehensible disconnections no one can figure out, even after several support tickets (still open) and forum posts. At first, the "solution" was to revert to stable. Now, there's no immediate solution, since the build is pretty much the same. So, in my case, this method sends me in a loop. Even if I revert to Stable, my problem persist because, inadvertently, a bug was introduced in Stable, prior to being handled in OB.

What happened to the Kiowa Warrior from Polychop? And that Blackhawk from those guys that did X-Plane stuff? Rotorcraft need some love...

The model is sound in most cases. Most industry players do this: one stable version and one "public test environment" (PTE, PTS, etc) where you test innovations with the help of dedicated Beta testers. However, this isn't what ED does. Not only is the Beta an open environment with no dedicated team guided by objectives and driven to improve and resolve, the process of transitioning to Stable DOES NOT solve the bugs found on Open Beta. Which doesn't make sense. You basically now have a Open Beta and a Delayed Open Beta, merging every two weeks. The way this should work was, yes, have two versions, but Open Beta or PTE or whatever you called it be based on specific goals and objectives, with a PROPER community guidance and dedicated forums with DEVELOPER feedback and much more regular fixes and hotfixes TESTED TO EXHAUSTION prior to public release on the Stable version. But we don't have this. So my suggestion is, just go Open Beta because the other takes two weeks to get new stuff... (and new bugs)...

While hosting, I've noticed that this is more prevalent with the F-18, and while it's on the ground. When it takes off, it appears to improve a bit. With some friends we also noticed something that may or may not be relevant. We noticed that this is more evident with Steam users hosting, especially with standalone clients connecting. With a standalone user hosting, we saw much more severe rubberband lag with Steam users as clients. Could it be a Steam vs Standalone thing?

Black screens, freezes, crashes. This week it's even worse.

But, may I ask... Why merge versions if you KNOW that that particular update has bugs in it? And don't tell me this is a third party issue, because the signal tone bug on the AIM-9X was there last week on Open Beta and it is now on Stable too, and the multiplayer Lag/Connection issues have been dragging for weeks, now also making a show in Stable. This is all ED, not third party. Why not solve the bugs first on OB and then release the fixed updates on Stable? It's not a stable version if it has unsolved OB bugs. It's just another Open Beta with delayed updates, isn't it?

The did postpone the latest Nav align update, probably because they messed something somewhere else. Or they found this particular bug. I honestly don't understand why they don't have a test team to try out release candidate updates. Then again, it looks like no dev team have them. Not even ED, apparently.

Just dropping by to say this issue is ongoing and no solution was given so far by ED.

Yes. Multiplayer isn't important internally apparently.

Reinstalling DCS world did nothing. After all this work, I still can't fly this simulator on multiplayer with my friends. I don't understand Eagle Dynamics silence. It's beyond me what is going on. I play several other videogames and simulators, including the much demanding X-Plane 11 on VATSIM and never EVER had these issues. Don't say to me "DCS is more demanding", because that's just a poor excuse for bad performance. If there's a fix for this, release it. If you can't figure it out, try something, open a simple server and try to host while playing with your friends. Invite me and test my DCS. Just don't hide behind this forum. It's becoming a pointless debacle coming here, speaking on my own, like a monologue.

I too have this issue. Since last update.