theIRIEone

First off, thanks for inviting the community to discuss and finalize the plan. Second, i don't care how long you call it EA or if you call it out of EA. As long as all the features will get implemented with priority over modules that came after it, i am very happy. Regarding the roadmap, personally i also would like to see core aircraft features being implemented and refined before we get more weapons. It's not that i would mind weapons, but seeing how potent the Hornet got when comparing it with it's initial release state, i think it is safe to say it is a completely different beast and very much multi-role capable. On the other hand, there's still core features missing such as CPL A/P modes, MDC w/ WPTSEQ options, MIDS/Link16, JHMCS functions, proper BIT, ASPJ etc. I am happy to see some of those made it into the EA part of the section already, but i'd surely love to see more of these core aircraft functions pushed to the nearer future if possible, in exchange for weapons systems. Obviously some of these weapon systems sound fun as well and the ATFLIR would be considered "core equipment" to a USN Hornet, but since this comes with a whole different can of worms i wouldn't want you to stop working on everything else just to bring us this pod as the next big feature. Stay healthy and thanks again for focusing on the Hornet for now.

I have the same problem as referenced in this post, and i have a timestamped video as track would probably be too large / long. (direct link as the embedded video's timestamp was incorrect for some reason and i can't get it to work proper) You will see CCIP displayed in Prog 2 on the stores page on letf DDI, and you will see it switching to auto the moment i hit WPTDSG. As per Wags' AUTO TO CCIP Video, the stores page should continue to display CCIP so the jet knows what program to fall back to when undesignate. As you can see, it stays AUTO and i switch to CCIP manually. Note that this recording was taken before Wednesday's update, but testing showed the problem consists in the latest version as well, referrencing this threat: https://forums.eagle.ru/showthread.php?p=4302306

Hahaaa i did not even test that yet. But i agree, that should not be possible as per Wags' video. Thanks everybody for confirming AUTO to CCIP being bugged at the moment, guess i'll post a bug report referencing this threat. EDIT: Bug report was already posted, i simply added to it

Thanks for confirming what i was thinking. I should've pointed out that when i wrote DDI, i was referring to the DDI Stores page displaying the release mode in the active program, not the HUD Repeater. Will edit in the OP to be more clear.

I tend to have the S/A page up on the MPCD around 99% of the time. Also trackIR user, but not hiding the stick myself.

During a multiplayer flight the other day i noticed that AUTO TO CCIP in Program 2 is not working. Am i wrong in thinking that it should work equally as in Program 1? My A2G loadout was 2*MK-83, i set up 2 programs, one for single release and one for multi release. JTAC asked for 2*MK-83, so i selected Prog2. Arriving at IP i designated the Target WPT, and that's where things started to go unexpected: Rather than having the DDI Stores Page displayed CCIP and the HUD displayed AUTO, as per Wags' AUTO to CCIP video, the Program switched to indicating AUTO as well the moment the WPT was designated (i only noticed that later on when watching the recording of the flight). Obviously, when undesignating the WPT, the release mode didn't revert to CCIP and i had to switch manually. I did not test if Prog 1 is working as intended at the time, but in Prog 2 it behaves unexpected to me.

The difference is that we're in a niche genre, not much (proper) competition. You gotta be passionate to deal with that kinda stuff on this level of detail ED is providing, and most companies are just out there for the money grab. Not saying ED is a company shying financial profit, but i think you get my point: Lack of direct / proper competition automatically means that hickups at release -as well as delays of release dates- will be more tolerated, because will you just stop what you are passionate about due to something freshly released into EA, that can be patched anyways? No you won't. I think at the end of the day we're happy that there is a company equally passionate about this stuff as we are, providing us with insanely detailed simulations of our favorite aircraft, even if not perfect - but constantly being worked on! I write that while being unhappy about various things myself, but that's nothing to be discussed in this threat imho.

It's times like these i feel bad about every time i pointed my fingers at ED for reasons that felt justified, and still feel justified when i think about them. Nothing was announced yet that would hint towards a delay, but the witch hunt is already on.. If there was a delay, yea that would be a huge downer because some of us are super hyped and i am sure people took off from work etc.. But consider if the announcement was something big / positive, y'all would look pretty stupid for not leaving your pitchforks in the barn for at least a few more hours.. However the outcome of the announcement will be, this threat speaks volume about us as a community.. Again. Unfortunate. Not saying that concern is not understandable, just saying wait out the announcement pls..

I wish ED would recognize that there are publicly available (declassified) versions of the NATOPS etc around, which have been uploaded/linked directly by their respective branches / governmental entities...

Rather off topic all in all, but since it's mentioned here: And that would benefit me in exactly what way? Last time i checked, UFCP input of the CRS was still taken as Magnetic anyways... Not to mention IRL they work with Mag rather than True as well.

It's the same with BALT, when you disengage the a/c starts rolling again, but as long as it is engaged and your bank is below 5deg, it will try to auto trim level for you. Upon you mentioning HSEL it comes to mind that, i think i encountered less of the jet struggling to stay level by itself with that engaged as well rather than just BALT. Maybe HSEL has more "power" to counter the roll, so that heavy asymetric loads with both enabled, you'd find the jet struggle less to keep level than with only BALT.. Would need testing as well. EDIT: Only read OPs sentence "It should stay trimmed where it is after you disengage the AP" now, i first started reading and then went for the TLDR part. Would be ace if we had something like this, would love to hear from SME's about that as well.

BALT does that already, but you have to be below 5 degrees of bank manually for the auto level (bank wise) to be in effect. Although i experience it struggling with heavy asymetrical loads, i don't know how the jet behaves IRL, could only assume that the FCS counters automatically since it also limits G according to weight / loadout.

- PLS ignore, i was convinced lack of proof and am not sure anymore -

"Fantastic" is really a subjective matter.. Gotta love the community for shutting down any legit voice of concern or criticism: you guys rock!

Yes, of course does adjusting the brightness knob work, and it even might make things green again, but that is not the point of this post. (switching to night mode in night time does as well) What i am observing is, that the DDI displays a different color in Day Mode depending on the in game daytime, and i don't think DDIs have color shifting abilities.. What should probably happen is the DDI being way too bright in day mode at night, not yellow, i assume. Obviously i don't fly in day mode at night, but that's not because of DDI color. It's because of the same reason you don't drive your car with interior lights on at night.. You don't want to be in a highly illuminated environment trying to see outside, that doesn't work.

While both DDIs where in different modes as you described, putting them both in the same Day Mode doesn't fix the problem but just leaves both DDIs yellow. I only noticed that because mission starts with both DDIs in day mode, as you can see in the screenshot attache to this reply.

1. Sounds amazing, i would love to see something like that 2. Would provide some variation, but do Redforce actually conduct strikes in Redflag? I always thought they didn't. 3. I don't see a way to implement the boat on NTTR map unfortunately, would love that but i'd rather fly the real procedures than having a Nimitz Class carrier sitting next to the Hoover dam.

As titled, since 2.5.6 Attached screenshot from "Dire Straits" Mission Left DDI: Day Mode - Yellow Right DDI: Night Mode - Dimmed Green HUD: Day Mode - Bright Green as expected

I don't think so, he just does his thing based on timing i assume, since you have a pre-briefed Takeoff time. However i figured that the distances to WPTs don't update anymore, albeit the WPTs themselves appear to be correct unlike earlier when we had to do the TCN INS alignment workaround. Didn't try the workaround in latest update yet.

Maybe that's old news, i never flown this mission pre 2.5.6, but the TGT coordinates given in briefing for manual input are off and don't equal WPT5, which is the given TGT WPT and where the target is located. The coordinates in briefing are East-ish of the Target, almost on the ingress (following WPTSEQ) feet wet. EDIT: i also noticed that i never got a reply from the carrier upon return within 50nm bubble, nor was a BRC somewhere to be found, but the boat had lights on and my estimated BRC from takeoff was still working out OK.

I can confirm for Malwarebytes what other users reported for other AVs now: Problem is solved, apparently by means of an update on the AV side of things. DCS working again without whitelisting / setting exclusions

I too am very confused by the phrase "CCIP bombing in auto mode" as i am under the same impression, either CCIP or auto (which is the defacto CCRP version of the Hornet), not both at the same time. Maybe they're referring to "Auto to CCIP" bombing? But that doesn't make much sense neither in regards to the bug (high drag ammo always treated high drag regardless of drag on/off?), to just fix it in 1 state / situation rather than the ammo itself? Hope somebody can clarify..

All i basically asked for in this threat. Thank You for letting us know!

Or, you could allow exceptions in your AV and "feel" much safer as well. Either way, that shouldn't be the point to be discussed here, rather that it's acknowledged that certain AVs red-flag parts of DCS (the .exe itself in MWB, and apparently a different file in Kaspersky?). I don't know if it's the AVs or DCS, but something is wrong and that needs to be addressed.

I don't think it's a virus neither, but still this is a problem. Update ran fine, but upon wanting to start DCS, Malwarebytes Premium popped up, quarantined immediately and prompted a restart. It's flagged as "Ransomware" however rather than "Trojan" here. Screenshot is out of MWB detection history. EDIT: DCS Version is 2.5.6.43503