Firebird1955

OK, thanks. I saw a new Bios come out yesterday and was trying to update. Thought I was missing something. Hopefully it will be out soon.

Maybe I am missing something, if so, please redirect me. Will there be an update of DCSFlightpanels to allow use of the new DCS-BIOS with the F-14B or did i screw up the installation, as I does not show in the drop down for selecting aircraft for the Saitek panel.

Agree 100% with that. There is nothing here that warrants someone jeopardizing their job. BTW did anyone notice the nose of the F-4E sitting just aft of the F-5F?????

Question concerning this. In our situation on MP Mission the host see's the two drogues out after the rejoin request as stated here. However, the clients seem to still show the older setup where the pre-contact command extends the drogue. Is that what everyone else see's?

OK, I need a bit of help. I just updated to 2.5.8 and got the usual "need to finish" command line. I do the CTL, ALT, C, open profile, double click AI Communications, then CTL A, then Delete, then CTL V and hit ok which closed the edit screen for the AI line. Here is where it gets strange: sometimes the apply button works, and sometimes it doesnt but no matter which, the next time I open VA, I get the same command line that "needs to finish. Any ideas? I see something similar above, but I tried the export LUA thing and that made no difference.

Probably why there is confusion as to whether it was installed already or not: New DCS World Features: Available now in the Open Beta and coming soon, are two new features for DCS World: Wake Turbulence. Just like the wake behind a ship, an aircraft also produces a turbulence wake behind it, with the strongest forces coming off the wingtips as vortices. DCS World will now be modeling these as an option and will add a new level of realism and challenge when flying formations, aerial refueling, and air-to-air combat. Battle Damage Assessment. Displayed along the left side of the screen when a target is damaged or destroyed by the player, these notifications appear. A red notification indicates a destroyed target and a yellow notification with a percentage indicates a damaged target. When in the cockpit, it can often be difficult to know if a target was hit and damaged. This optional feature is provided to remove that mystery. Really doesnt specify what is and what is not. Thanks for the clarification Wags.

https://forums.eagle.ru/showpost.php?p=3764369&postcount=40 First, I cannot find any mention of a hotfix (I am sure I missed it) and second, I see no mention of the prevention of such hotfix in the weekend news release. I am just curious as to what is being fixed without guessing.:D

Thanks...... Probably a training issue on my end, :book:. Although, why wouldn't VR issues count as bugs just as any other issue does?:huh:

I have the same issue in 2.5.4 and it started with the update to 2.5.4. There is a thread in the VR bug section about it which has been going since that update. Windows 10, Nvidia graphics (up to date) VR Oculus rift CV1. All Driver updates are jus done as updates. I had not piped in as this post was made in that thread so thought it was being looked at already: https://forums.eagle.ru/showpost.php?p=3728259&postcount=37 Not only do I have the issue, but every single user (6-7) in my VFS has it as well. Only fix was to turn water to Medium. Also, I am curious why there is nothing but dash marks for the newest thread info and post # on the VR thread for bugs. Is that intentional or just an oversight? It almost makes it seem the thread is closed even though it is quite lively once you open it. :music_whistling:

That was my thought as well, then I read Wag's mini-update about the 88's next week so wasn't sure. Thanks all

Simple question, no hidden agenda, just curious.

IS this mod still functional with 2.5.4 update??

Maybe this will help; https://www.google.com/search?q=F-16+Aces+II+angle&safe=off&rlz=1C1GCEU_enUS821US821&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi2u5aqtOTfAhV8IDQIHSoIDbkQ_AUIDigB&biw=1325&bih=637#imgrc=iyDbvUiT5lf_WM:

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............