BlueAngel

SkateZilla ED needs to elect a Community Manager just to relay this stuff to the community. The phrasing here is different, but Mr. Wagner clearly stated this would be featured in the "next update" (watch the video and read the updates on Facebook). Quoting the text on Facebook posted on June 30th: In the next update for our Hornet, we are making some changes to rockets and cluster bombs: 1- Rockets pods can now be set to Single (S) release setting in the Mission Editor, (...) I don't mind the waiting. I understand these things take time. But I really wanted to have realistic expectations. That's all. I won't be bothered if there's no new paint job or rocket option today. Just don't raise expectations. That's all.

I don't understand why it releases salvo in the first place by default. Is it mimicking real life? All other modules fire singles by default.

Spawned hot and no issues whatsoever with the gear.

I wonder if there's multiple versions of the Hornet under development and they need to compile them into one public release. If that's the case, then Mr. Wagner will have a different version from us all. I remembered this was evident when we all reported the hot rearm not working for ground weapons and Mr. Wags said it worked fine on his side. After some years working on beta testing and debugging in other simulators, I must say this isn't good practice. It's always advisable to work with one single developer build in any stage.

Unfortunately, this wasn't included in Update 6... :(

For those that don't know what I'm talking about, Mr. Wagner did clearly state that the Rocket single fire mode would be available "in the next update" for the Hornet. The option would show up in the Mission Editor as described in this video. What did I miss since I don't have that "Additional Properties" tab?

I tried renaming that folder. I tried just deleting metashaders2 folders. No joy. Still crash like crazy. Again, either to the desktop or to the main menu. I am also getting hangs from entering multiplayer sessions. Could this really be a DX11 issue?

Hi, this is now a constant thing for me too. I don't know what to do anymore. Tried repair, tried driver fresh install, tried turning the firewall off, tried a clean up, tried every suggestion here. It either crashes to desktop or to the menu. See attached log. It's constant, over and over and over. That's just my latest try. dcs.zip

Not to be picky, but it would help to have them clarify this and not just speculate. I would say nothing was added. I would say that they are dispersing a bit considering it's just 8 guys and now they have 5 more projects while the M2000C and AV-8B still need work. But I'm a pessimist.

I really wanted that Maverick uncage issue and the overwhelming beacon light fixed. Since sometimes the changelog doesn't include Razbam's modules, I was hoping anything new came with it.

I can corroborate this also happens to me. May I remind ED that low level flight is not a stunt, from aborted landings to terrain masking, it is very important for combat as well as normal and abnormal operations. Remember the DCS Hornet had (mostly still have) the flaps issue, where the drag/lift logic was somehow exaggerated and some would say inverted, so this could be fixed too.

I started another thread with this exact issue. +1 ED's responded to this at any point?

Anyone?

Hey there I got these extreme rubberband lag issues, where either AI or player planes just seem to move around, like crazy in all directions, sometimes for miles away, other times just sinking in the scenery and back. On the F10 map I can see all planes and vehicles zooming all over the place. This happens in pretty much all online sessiosn, no matter the ping. I also get some random freezes after this happens for a while. It ultimately will crash me back to the menu. This seems to be related. I am thinking about a syncing problem, possible something related with netcode. I have a fairly good internet ISP and didn't have these issues before. It all started after 2.5.2, F-18 and PG updates. Can anyone relate to this? Any suggestions?

I think this is how the RWR does work. It gives you bearings, not distances. I refer to the fact that within maximum and optimal range, the missile will go ballistic (as intended) but will not always behave as expected, not leading the target properly or adjusting to the aircraft´s radar feed. It could be a matter of weapon limitations, but it could also be something related to the flight and prediction model. Or just the radar itself. Added the brightness issue. I can confirm it does that. As for the DDI turning off during Engine 1 startup, I don't know if this is a true feature. Airliners I fly also do this upon turning on or off of the APU or generator power, simulating the buses tripping (AC to DC power, for example)

I get this too. I feel that it can be mitigated if I don't go full rudder left or right, just increase the turn incrementally.

Updated with fixes. Please help me continue to curate this thread.

I can't believe this hot rearm/weapon BIT issue wasn't solved with this latest update. Is it a hard thing to handle? (I'm not criticizing, literally just asking if this is a hard issue to tackle)

Thread updated with further bugs reported and WIP Continue sending your suggestions and inputs to this list.

How do you actually bind them? I can only place up to 4 AI planes and they all end up crashing into each other. In the mission creator you can't select the parking position, it's always on "auto".

It wouldn't affect the radio source bearing of course. But if your alignment isn't correct your position and radio's relative position would be offset, because your inertial system wouldn't know where you are exactly. If I'm not mistaken, the auto-start sequence does not perform the correct alignment and places you in IFA mode, which doesn't seem to be as accurate. Try a normal start running ground or carrier alignment.

I am sorry but I've used the TACAN on the Stennis and it appears to be as accurate as it can be. Are you performing proper INS alignment?

Updated the first page list with further suggestions from you guys. Again, this would help a lot of people if the admins either pin or create a similar post with their own list.

I've updated the bug list with your suggestions. Would it be nice to have this pinned?

Hey It would seem that so many bugs and work in progress items are repeated in this section. Can I ask that we create a simple bug/WIP list so that people search for what has already been reported and what is WIP and will be implemented later? Reported and Known Bugs FIXED - Hot rearm does not recognize new AG weapon types. - "DEGD" indication on Weapons BIT (connected to the above issue) FIXED - EHSD Map OFF option is not available. FIXED - F/A-18C Hornet does not log flight hours. - "Bump" sounds after Mach 1. - Carrier catapult takeoff afterburner issues - UFC comms sometimes doesn't register the input of new frequencies. PART FIXED - ADV-RSET warning on the left DDI. - Inability to adjust AMPCD brightness, contrast etc - Length of time to hold UFC buttons to activate them - Oscillation after catapult launch - HUD blurriness (in 4k screens) and text slightly thick FIXED - In A/G bombing in CCIP mode, after pickle it will switch into AUTO. - In the Cold Start Training mission, for one of the steps, the voice switches to Chinese - ADF static sound persistence after being switched OFF. - CVN-74 jet blast deflectors don't raise for cat launch. - Radio transmissions sometimes don't go through, demanding multiple tries via radio menu. FIXED - Flying with fuel tanks can cause a random freeze. - EHSD brightness control doesn't work properly. Reported, but not a bug (Work in progress) - Jammers are not implemented - Parking spots are bugged on the CVN-74 - Multi-display monitors not supported yet - MFD export doesn't work yet - AIM-7F/M Sparrow accuracy needs further work - Approach angle of attack behavior needs further work Help me out with further issues you may have seen reported and/or classified as WIP. UPDATED: June 10th 2018