Firebird1955

Interestingly, I had a situation tonight in MP that I could not get the Frequency to change in SRS when making either a Darkstar, or Texaco call. The system would actually call out, but it was on wrong Frequency.........The only thing that I changed to fix it, was to turn the new ICS hotkey off (uncheck), then went back into sim and all was well. Using easycomms ON. Anyone else able to link a not call to the ics checkbox in the Vaicom pro configuration EX tab? It would work after I used the menu to make the initial call (which DID change the frequency)...

Another update to Vaicom dropped today.

Just curious, did you also download and update the Rio download for Vaicom? It is not included in the Vaicom pro update.

You remapped a button.............................:megalol: Sorry, couldn't pass it up. Something with the ICS switch??????? shooting in the dark though.

A note in advance. You must redo the finish, delete, and paste process through editor for the new commands to show. I didnt get a warning in the voiceattack screen, but it had to be done.

Try this Dispatch...........

Great. Glad it worked.

If the finish button is orange, then you will have to press it and follow the procedure for adding lines in the editor. It took a while, but you have to actually do the complete procedure of deleting and pasting the commands as stated in the box that opens when you click the finish button. Good luck.

Go to the editor tab of the Viacom control panel (Lt CTL, Lt ALT, C) and see if the finish tab isnt orange. That is what I had to remember how to do. You have to update the profile just as you would with a new command phrase. Hopefully that helps

Any input from the ED Team on this issue? Not that I do not believe the gentlemen above, but according to the update from yesterday, it said the INS Was FIXED. Nothing about a WIP. INS set correctly on Autostart. INS alignment fixed. That does not align (no pun intended) with what has been said above.

Says the person sharing file has exceeded their sharing limits..............

Understood. No rush.

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: