theIRIEone

I wonder if this one is related to the thing i described here: https://forums.eagle.ru/showthread.php?t=276770 The reason for the ghost target (box) was a different one, yet the result sounds somewhat related...

+1 i would like the team to have another look into this: Feels wrong comparing the Hornet to other planes sporting the same M-61, but being able to get IN RNG much, much earlier... something's off, or is the Hornet just THAT bad compared to other fighters?

Requested trackfile can be found at https://drive.google.com/file/d/1bGAiQaHSKaolP9lDabxVXgghK2sxXcgr/view?usp=sharing because 31MB file size exceeds limit on forums. I also have the video of the flight still on my HDD, can upload that as well if needed. Thanks for checking.

Hello, One of these days in a multiplayer flight testing the SLAM, i had a to switch to A2A temporarily and down a REDFOR plane. After that i locked another A2A contact, figured it was friendly and returned to my A2G duties.. To my surprise, a ghost box of the last locked A2A contact remained in the HUD, even when the A2G TGT diamond was displayed at the same time. I found myself switching the radar off completely, didn't fix it. I am not sure what fixed it eventually because when RTB i switched master modes (master arm and toggling between A2A / A2G mode), A2A weapons and radar on / off all at once kinda. at one point, the ghost image finally disappeared. See attached screenshot, and pls disregard the wrongly set up SLAM/DatalinkPod..

Honestly, i don't even care how they call it as long as i am convinced they are actively working towards completion. All those naming issues of different modules in different states is just another piece to rub and gain tension on for the community, and we are rubbing and gaining tension enough already as is

Well, the originally stated goal was to replicate a US Navy Lot 20 Charlie Hornet, not even a USMC one. The USMC one came into the picture only after they announced the delay of ATFLIR in favor for the LITENING, which is / was a whole different topic for itself. I completely agree on the coordinates needing to be displayed, i guess it's FAC(A) with a JDAM for now, until ATFLIR arrives or ED change their mind. Matter of fact, not just as FAC(A) but everytime you carry a LITENING you kinda need a JDAM if you want to create / pass WPTS currently. (MIDS/LINK16 updates might solve parts of that issue at least?) As it was much faster to produce than the ATFLIR, because the latter one needs a new rendering engine (which also will be implemented in the LITENING when ready afaik), and it already existed in the game, i thought this would be exactly what they'd be doing! Adding some minor tweaks here and there maybe... Instead they apparently built this thing from scratch(?), but surely not because the Viper can carry this one as well... totally unrelated :music_whistling:

That is not true. I never said we was best buddies. I said he is not random to me, like he is not random to others in this threat neither. The real problem is ED misleading their community over and over again, be it unintentionally or not. As i said earlier, now that we have a Spanish LITENING, i would open that "ILS replacing ICLS" can again, as the argument back then when people initially asked for that was clearly made: "We are simulating a specific USN version, the Lot 20, and as such it only has ICLS, unlike export version like Spanish Hornets, which would have it replaced"... I don't want that, i never signed up for a Spanish Hornet, and actually can live with the pod being Spanish and the aircraft being not given its only temporary, but am noticing that claims are always changed, and when you point that out somebody comes trying to defend ED, ignoring facts, just picking the one part to focus on... No matter how ridiculous things get.

Holy Moly, this is one display of ignorance only the masters of ignorance can come up with.. I hope this represents your personal opinion and not EDs. Sorry i don't know what the term DCS Ground Crew means on this forum, so i don't know your affiliation status. You start off with stating the OP is "sort of correct", still refusing to acknowledge the OP is VERY correct. Then you go on and call him "random dude".. While this "person" may be random to you, he is not to everybody contributing to this topic, i for one have flown with him many times as we've been squadmates before, and still am flying with him from time to time. And i am sure not being the only one here to do so. Then you go on to diffarm the 30mins research he did. Well, he needed only 30mins of research to actually debunk the claim that we're getting a USMC LITENING, which was claimed by ED for months! What does that tell us about trustworthiness or truth about ED's statements made towards us, their community?? Yet here you are, attacking the OP and the community, closing your eyes not seeing facts and causal connections. Then you follow that post up with: ...which really sounds like "i didnt ask you to prove, and i dont want you to prove me wrong, so i can continue to make assumptions." Good riddance, again i hope that reflects your personal opinion and not EDs, otherwise we would've reached a new low for sure.

I *think* it's planned for later in EA, but i might be wrong. While i completely agree with you, i also kinda got used to "baby steps" when it comes to new modules: 2 years from now, there will be so much added that the initial EA release state will be perceived as very bare-bones (it actually is, but launches are still glorious). Just remember how the Hornet was equipped when it was initially released, and look at it now. Good things take time, and very good things apparently take very long time.

Happy to say thank you as well. Had a rough time after the update, but now everything's cool and i can enjoy the product after catching some sleep. Still a long way til completion, but i love what i see so far.. the deck crew at launch is fantastic, really lifts immersion to never seen before dimensions, makes us crave for more of that caliber... Great job!

To be honest, i don't think this is correct, given the fact that there is a very long list of items to be added to the Hornet after it will leave EA by the end of this year (at least that's what is communicated as planned).. Saying that, i wouldn't be able to define what EA means in ED terms, something different every time it pops up? That being said, i could care less about which is called what as long as i know the modules are still being developed. Most important in regards to OP question, you also mentioned: always open beta first, regardless of module.

I am completely confused in regards to what kind of Hornet we have modeled now. Initially right after release, when people asked for "proper ILS", the argument was made that we have a LOT 20 USN Hornet, and as such it only sports ICLS, unlike SPANISH Hornets, which would have the ICLS exchanged with ILS. Then, we got the LITENING rather then the correct ATFLIR because "reasons", making it not really a pure Lot 20 Navy Hornet anymore, but still a Naval Hornet (more like USMC, but that's also a workaround because centerline LITENING and carrier ops isnt a thing etc, we all know that debate).. Now, the LITENING turns out to be the SPANISH one? So, do we get our ICLS revoked these days because we're clearly not modelling a USN Lot 20 anymore? Or will ILS be made optional so it fits the LITENING we have now? Then again, ATFLIR is still on the list, leading to a USN Lot 20 again... I am SERIOUSLY confused now.

OK so, not sure what it was or why it works now, but i kept trying and the latest clean install appears to work just fine. Had another CASE 1 just a few mins ago, with all owned modules installed. I wish by now i had seen all 4 boats and also did CASE 3s, but i did nothing else but problem solving since yesterday evening (its almost 2am here again), making me dead tired and postpone all the SC goodness to another day... Consider this problem solved for now. If it returns i'll just open a new topic and refer to this one. Thanks.

Thanks, i'm still on it, but chose to "repair" this time instead of deleting and trying again. Appears to be running through now, at least came a lot further already.. fingers crossed

In process of trying to solve my original problem described here https://forums.eagle.ru/showthread.php?t=274238 i am currently trying to re-install again. I am on the open beta branch ever since i joined the DCS club, but getting the same error message as the OP now.. tried multiple times already.

That. Also, do you get any error messages? Is it crashing and quitting or does it freeze?

Thanks for your reply. I just tried adding the logfiles, but the forum uploader throws invalid file errors (see screenshot).. Will upload to gdrive or something and edit OP within the next 5mins. EDIT: added link to logfiles in OP

Hello people, please bear with me while i try to describe the problem. Ever since the open beta update of yesterday, i get the weirdest issues with dcs.xe being unresponsive, and me being unable to kill the task. Currently i have the whole DCS folder deleted for a second time since the update. I try to be chronological, without going into too much detail regarding the earlier attempts of fixing the problem since there was a fresh re-install in between, which worked just fine briefly (more on that further down). Prelude / previous issues after update, before first re-install So, after the update, my DCS always got stuck on the splash screen. I am not referring to the full screen black background ED screen, but the first one with still having the desktop in the background. When trying to kill the task, it just refused to get killed. I know patience goes a long way with computers, and its not that i didn't wait for a few minutes before trying to kill the task. But even if i didn't, i should always be able to kill the dcs.exe using task manager, right? Only thing coming to my mind at this point was restarting, but after i did that, i received an "only 1 instance allowed" prompt, leading me to check task manager for a dcs.exe. To my surprise, nothing was seen there, so i checked resource monitor: and there was a dcs.exe living in my memory, and every time i tried ending that process, i received an "access denied" prompt! I then restarted with my PSU switched off for 3mins, after starting up again same thing: a "hidden dcs.exe" in my resource monitor's memory tab. I then tried deleting DCS, but couldn't do so, not even by manually selecting the folder and deleting it that way rather than clean uninstalling, because again, windows prompted me "access denied"!! At this point, i ran a repair, and restarted, which at first looked promising because there was no more dcs.exe "hidden" in my resource monitor., but actually i just encountered the same problem, with the only difference being that there was 1x dcs.exe in my task manager (unable to get killed again), and 2x dcs.exe in my resource monitor's memory tab after trying to start up DCS. BTW when i say resource monitor, i refer to the built in windows one, not a 3rd party software. I only was able to delete / uninstall after running another repair and restart, because that at least got rid of the "hidden" dcs.exe, as long as i didn't try to start DCS. Here starts the current part of the problem I then did a fresh install, and me being eager to test the SC, i only downloaded the Hornet and the SC module at first, exchanged the FLOLS.lua to get rid of that annoying pop-up when in the groove, and had a couple of CASE 1s.. i was sooo glad that the issue was finally resolved and was enjoying the SC in my Hornet to the fullest. Then, i shut down DCS, restarted it again, no problem. Started the install of all remaining modules i own, namely: NTTR, PG, A-10C, F-5E, a couple of campaign and the SU-33, which i never bought but i believe came with the SC? After seeing that DCS shut itself down and started the install process as it should, i was happy and left the house... only to come back to being stuck on the same splash screen again as before, again without being unable to kill the dcs.exe. Only difference to the previous errors was that this time, there was only 1x dcs.exe in resource monitor and 1x dcs.exe in task manager, so that's progress i guess? Either way, i again tried repairing, restarting the PC and starting DCS, but encountered the same problem. Eventually, i did a last repair because again, i wasn't able to de-install otherwise, because again my access was denied (while i could still open and alter .lua files, which i did just as a test, i was unable to delete the folders - same as before the fresh re-install)! In the meantime, i ran "chkdsk /f" on both my windows and dedicated DCS drives (both ssd), everything's ok here. Now i am completely out of ideas, so are my squad mates, and i went crazy, came back and went crazy again.. I am totally clueless of how to proceed next and am asking for help / support here. All i wanna do is fly my Hornet from the SC, but not necessarily on Caucasus since my squad's OPs are on the PG map usually. At this point i don't even care if i can't reinstall anything but Hornet related stuff and the maps i purchased. Additional Info It might be worth nothing that i did the update rather early and also got caught in the wave of authorization problems initially (as many others did), but i was under the impression these where resolved after a while, and certainly after my fresh re-install (albeit coming to think of it again, i am uncertain if the F-5 BFM campaign showed up?) I documented the issue on the official discord yesterday, up until the point i first re-installed. It was a rather hectic situation / evening obviously because a lot of people had different issues, but maybe any of the admins / helpers remember the issue from me posting there as well. Might be related, might not be: when there was that antivir issue a month or so back, i allowed dcs.exe as an exception, and it still is allowed as such. TLDR DCS gets stuck on splash screen and dcs.exe is locked and unresponsive, refuses to get killed. Spent hrs troubleshooting, did a fresh re-install with just Hornet and SC, worked just fine. Installed remaining modules: stuck at splash screen again with unresponsive dcs.exe, again unable to get killed. Repairs don't help, so currently de-installed again, looking for help. EDIT: latest Logfiles via gdrive because i was unable to upload here: https://drive.google.com/open?id=1qZTvLU-O3hwKgbm7cNaF6Jot_Cj_1tif EDIT2: I've seen ED team asking for processor in use in other game crash topics, so here's my specs (not great but always ran OK , SP and MP): CPU: AMD Ryzen 1500X GPU: Nvidia 1050TI 4GB (Zotac OC edition) RAM: generic 16GB DDR4 SSDs: Evo960 NVMe for Windows, Intel 540s for DCS in case you need more specs let me know and i'll look for the exact MB, PSU etc names

I actually completely agree with this. After all we might be sitting behind a screen in our comfy chairs, yet this is a simulator and we're striving for upmost possible realism and immersion. At least a part of us does. There's always the once that just get in a jet, shoot some stuff and get out again.

I don't really follow the Viper as i am not interested in flying it really, but i guess when they said that it's development would slow down and they (finally) refocus on the Hornet, they really meant it.. You guys don't even get a hotfix now?? :megalol:

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.