Firebird1955

On a multiplayer mission last night, we had a similar issue, except that the gun continued to fire after the trigger was released and did not stop until it was empty. This is not the first time, nor the only person that has had this issue, and we cannot be sure if it is MP or both, but mostly MP. It is also difficult to track as it is intermittent in nature. I searched but this is the only post that I found which even suggested anyone else had a problem. I am completely unclear if this a procedural issue or a bug. Has anyone else had this issue?

Same issue here exactly. Did you ever get an answer to the issue? Even after I reposition to a different location and save it, it places it in exactly the same place (cut off as well) but colors do change. I do not want to have to deal with a failed integrity check so would like to get it work in the saved game section.

Doubt it has anything to do with the F-18 module itself. You should try this thread as it looks like there may be others with issues as well. I am to the patch before this mornings update and it all is working pretty well. Especially after I updated to 2.5.5 https://forums.eagle.ru/showthread.php?t=198297

After doing a search for HUD Brightness, I found 25 references. I looked at several which have requested HUD brightness since 2017 and do note that the HUD is listed in their 2018 "In work or Planned" list on the update post (Various HUD updates and corrections). I did not note any sort of timeframe or confirmation that it would actually be done, and since it would be more of a feature than a bug, probably another WIP issue.

Wow. Now I do not know how to use the forum. How would I have found the initial report of the shadow issue if I had not used the Search function? In fact, I use it regularly which helps me avoid situations that this seems to have been turned into. I also take advise, such as the advise to use PM to get things looked into without getting a messy forum thread going. Of course if no one answers the PM, what recourse do I have left. I received the answer to my questions, and thanked you for it. Not trying to make anyones job around here harder, and, contrary to popular belief, I understand the process since I have been using DCS Beta since the 1st A-10. Lets move on

It is a shame that it took 4 months and 4 pages to find out it is a known issue, but Thanks

But the intent of the initial post WAS about 2.5 and fixed high shadows that could not be changed. It was not looked at since its first post in June. If you look in your PM's, I asked you specifically to look into it last week with no response whatsoever. What am I supposed to think?

Read my specs............1080ti should be enough. Maybe you have a grand to throw at it. I do not. I also understand that it is "In Work" (been a member here for a while so should be a given) but that does not mean that we cannot expect customer support for issues that are happening. I do not expect a same day, or even next day response every time, but good grief, 3 months......... Here is another thing. The Mods cannot respond to issues over time, but they can move this to the darkest hole that no one looks at almost immediately. This post started in the 2.5 forum so it could be seen. Guess someone did not want that to happen.

It seems that sometimes issues brought up within the Bugs and Problems section of the 2.5 section are either ignored or overlooked leaving no recourse but to repost and ask again. This has been done on at least one thread and it has gone on since June 4th. At that time, it was posted that shadows (exterior) for the hornet were locked to high no matter what level the UI has it set to in game. This has 13 posts on it ranging from June, and again in September without a single response from anyone from ED (Moderator or tester). I sent a PM to a senior moderator to ask for assistance, and that PM has neither been acknowledged or shown any responses within the specified thread. IF in fact exterior shadows are locked in high for the hornet will cause an extreme performance hit to the program that medium to low end systems will find intolerable. IT would also explain why FPS on the ground at Nellis start at 22-25 and climb as the shadow decreases after takeoff. Not looking for an immediate fix or anything, just want someone to acknowledge it is being looked into so we can get it fixed.......... Steps off soapbox... Thread in question: https://forums.eagle.ru/showthread.php?t=211449 :helpsmilie:

Bump... I am amazed. This thread has been going since June without a single ED mod/tester response, within the Bugs and Problems section, that I saw. I have even PM'd Nineline to ask him to look at it. Why doesn't this deserve a response like any other problem/issue?????

Has there been any movement on this front, or is it on the back burner??? I still see the same thing today as was noted here in June. Extremely high detail shadows in F-18 no matter what the settings are in the UI.. Could we get a follow up?

I have searched the Forum and have not located this issue, but I know it did exist early in the new NTTR map lifespan. Mission entry on the ramp near Covered parking (West Ramp) in F-18C. Numerous Static aircraft parked on the ramp to include F-18, F-15, etc.. Once entered, FPS is around 22-23 FPS (VR, Oculus), but increases slightly to 27-30 once on main taxiway moving South and a little better once on 3R runway heading for departure. Once airborne and over racetrack, FPS stabilizes at 45 and stays for entire flight until entering the overhead for Nellis again, then back to the 22-23 FPS. This was observed in both a single player state and MP with 2 clients (Both showing similar FPS). As you can see from my spec's this is a higher end system, and to be honest, when flying the F-15C out of Nellis I did not observe the same issues (Older DCS 2.5 versions). I just find it strange that I do not see others with the same issues. This was done with the latest DCS version (OB, HF3) which may shed some light on the issue. Maybe I just don't know where to look on the searches............

Pre ordered through B&H at Oshkosh on 26 July and they still (as of this morning) cannot tell me when they will have them in stock. Just shows backordered.............:(

Voice attack with Vaicom pro add on or similar to reduce keyboard workload. Especially to get away from the Fkey menu issues. It does work, at least for me.:pilotfly:

Just as an FYI it was beta. Thanks for the info.

I have observed recently that when 2 tankers (Texaco=C130 and Arco=S3) are airborne at the same time when I call for intent to refuel, the tanker that is selected is always Arco even when I am very near Texaco. When I say "Texaco" pause till beep then "Approaching to refuel", it will only send a message to Arco. IF I say "Select Texaco" release TX and then say "Approaching to refuel" it will change to Texaco every time (instant selection is checked in preferences). This only seems to apply to the situation with multiple tankers as other aircraft/ATC within the mission are recognized as always, with a simple Callsign, pause, then command. It wasnt this way until the update that changed the key bindings, at least on my end. I tried changing the device to "13" from "38" as in earlier posts, but could not contact anything until I put the "38" back in. This is not a major issue as I can easily say "Select Texaco (or Arco)" prior to intercept, but thought I would throw it out there in case others are seeing the same issue.

BD, It has to be registered like Viacom pro and you should have received a seperate "key" in the email for the chatter. If it is in the app folder as described earlier, then (Assuming that you have a Warthog throttle) you should be able to push the comm button "IN" and it should start/stop chatter as a toggle. Hopefullly this helps.

Chatter key goes in same box as the Vaicom key went in, then email addy. Somehow it knows the difference. Then, if you look C:/voiceattack/vaicom/apps (could vary) there should be a chatter.dll (I believe that is it). If it is not there, then move from the chatter download to that folder.....At least that is what I did to make it work.

I have been playing with it as well with some success. In my case, while I am using 2.5.3, my Vaicom.export.lua had a version of 2.5.0 with no F-18 listed (probably a poorly executed update on my part). I uninstalled vaicom from voice attack as well as the associated export.lua files in saved games and app data (anywhere I found Vaicom.export.lua). I reinstalled 2.5.3 and when I checked the Vaicom.export.lua it had an F-18 listed. It appears to have corrected the failure to send the command to DCS and all went well except for being able to switch between the two tankers I have in game. This could easily have been a failure to set up the VAICOM panel up correctly. I made no changes to any of the export.lua files, just let them regenerate...

Hmmmmmmmmmm... Wonder if MP host had easy comms off (he said he did not, but it could still happen)...

Probably gonna have to be the .lua guru as I had easy comms on and had the issue. Didnt try easy comms off though..........was also using multi to single in the VAICOM setup.

Agreed. I did not try other airframes but DCS did have the following in the changelog from the 18th so something was done to the radios. COMM: Manually entered frequency will no more appears in channels settings Hopefully it will be that simple..

First, let me start by saying this is NOT a flame post, or any other form of Negative observation... This weeks Mini-update (7/13) Update Changelog (7/18 ) and Weekend news (7/20), along with a few other posts has me confused as to what actually did/didn't make the update in relation to the F-18 this week. Wag's notes (7/13 state that the following would be in next update: 1- Aircraft no longer slide on the carrier deck, at any carrier speed. 2- STT track will not switch lock uncommanded. 3- RADAR SIL (radar silence) and STBY mode has been implemented. See image. 4- RWR display logic has been further improved, with critical threat lines added. See image. 5- Option on ME to select single or ripple release (was not in fact merged for last update) 6- DUD cue added for when HT or fuze setting is below current aircraft AGL. See image. 7- RWS page SET and weapon and count added when a weapon is in priority. See image. 8- Night Vision Goggles (NVG) added. See image. 9- Instrumented Carrier Landing System (ICLS) added. See image. 10- Landing gear drag lowered. The Changelog provided on 7/18 said the following made the update: Second (third, fourth) client now can be spawned on 2nd (3rd, 4th) catapult when 1st CAT is busy Radar in STT mode will not jump to another target without players action Radar SIL and STBY modes realized S (single) and R (Ripple) weapons loading options added Selected A/A weapon is no more displayed on radar page in RWS mode Night vision goggles added COMM: Manually entered frequency will no more appears in channels settings Random crash when F/A-18C spawned on carrier catapult in multiplayer fixed Carrier ICLS system realized Radar: roll and pitch stabilization system improved when user changes elevation by discrete button commands Then Today (7/20) The Weekend news says the following: Aircraft no longer slide on the carrier deck, at any carrier speed. STT track will not switch lock uncommanded. RADAR SIL (radar silence) and STBY mode has been implemented. RWR display logic has been further improved, with critical threat lines added. Option on ME to select single or ripple release (was not in fact merged for last update) DUD cue added for when HT or fuze setting is below current aircraft AGL. RWS page SET and weapon and count added when a weapon is in priority. Night Vision Goggles (NVG) added. Instrumented Carrier Landing System (ICLS) added. Landing gear drag lowered. The weekend news is exactly the same as Wag had posted on the 13th yet when questions about the Landing gear drag issue, ED Tester said it did NOT make the update. Additionally, during a MP mission last night, the aircraft were still sliding all over the deck with the speed above 19 kts (we reduced speed from 27 to 19 kts and sliding went away immediately). Now I fully understand that even though some things are mentioned prior to an update that things change and they do not make it. I also know that some things get fixed sooner and are put in. What is confusing is when items pointed out for an update do not show in the update changelog, but DO show up as updated in said update in the weekend news. PLEASE TAKE THIS AS CONSTRUCTIVE CRITICISM AND NOT AS A NEGATIVE POST!! This is an amazing simulation that has so many moving parts it is unfathomable to many of us. Everyone should be proud of producing an outstanding platform with the F-18 release. Thank you all for what you provide...!!!

Having the same issue here as well. Mission last night (MP) where clients both had the issue of VAICOM not sending command through DCS after it shows as recognized in VA. Funny thing is that the host did NOT have an issue. WE checked easy comms, and all of the normal things that cause the issue but nothing changed. It was exactly as the others have mentioned. It cues it up, but unless you hit a transmit key (Interestingly enough the one I had to push wasnt even mapped in voiceattack) it will not transmit it out in DCS. It is as if when they changed the key bindings, it affected the transmit on the radio. Verified that no key was programmed to the Comm1/2 transmit keys in DCS profile. Also noted that simple commands (canopy open, NVG toggle, etc., which have been added to profile work without issue. It seems to only be VAICOM AI Communications commands that are affected (Tanker, Stennis, Crew, Darkstar) I will try the same mission tonight in SP to see if it happens to be a Multiplayer issue.....:joystick:

Ok Thanks for the reply. This was on a private server and it was always the last part. Just so I understand, it delays 10 minutes at the start, so the last 10 minutes are not there for the client. The host seems to have the whole thing always.