PeneCruz

Thanks appreciated

When you place a static Harrier down on a ship and link to unit it appears slightly nose high in the X axis, not level with the deck. only occurs in Multiplayer and when linked to a ship. All clients see the same thing. suggest a simple EDM error for the AV-8B static model when synced in multiplayer.

Hey, thanks for that. Yes it’s reported. Something to do with the new chocks logic on the Tomcat I assume. We have taken a bit of a break over the Christmas period from testing and coding. It’s on our list of things to tackle, along with some weird PTT actions on the Viggen, A4 some WWII modules and the KA-50.

Hi All With DCS moving to 2.8.X for both Stable and Open Beta previous versions of VAICOM PRO will no longer work. The Community Edition 2.8.1.X is available from GitHub and is being actively maintained. To download the latest release head over and grab it. Please read the readme for the installation instructions if you are upgrading or the manual if it is a new installation. https://github.com/Penecruz/VAICOMPRO-Community/releases

Another option is to make Phonetic aliases for the troublesome ones through the VaicomPro editor.

This is a known issue, we are working on fixing it, it's related to the Comms menu supression. Actually looking at it now.

We are working on a more permenat fix now that Hollywood has open sourced it. We are also putting together a Dev team to keep it running and potentially add to it. It will take us a few days to get a clean .dll that will make it functional in DCS 2.8.xxxxx with minimal messing around. At the moment there is a fix on our Discord. (with messing around) https://discord.gg/7c22BHNSCS I would like to publically acknowledge Hollywood_315 for the awesome advancement of VR flying in DCS. Without his work VR DCS would still be fringe at best. He bridged the gap with Vaicom Pro. Thankyou on behalf of the rest of us.

It's a tempory fix, just patches the lua's and stops Vaicom updating them to the broken ones. you must delete the old luas hence the removal and reinstall of vaicom (you can do it differently but this is a failsafe) DONT RUN DCS. Then launch Voice attack and activate Viacom Pro it will patch DCs with the broken luas, now add the zip file scripts folder to your DCS main directory (NOT SAVED GAMES) and it will work. If you don't follow the instructions regarding DCS path above the fix will get overwritten. We are working on a more longer term fix to avoid the whole routine. The Community Discord https://discord.gg/7c22BHNSCS

I have fixed the poor below 800ft VR performance at low level by turning DCS options Terrain textures* to low. I now get smooth FPS in VR over the entire map. This is great as it means it just requires some optimization. I do have quite a high end system so user experience may vary! but I was dropping from smooth flight to stutters every time I descended below 800ft AGL.

Awesome, perfect for our ELINT script. Nice work and thanks

Maybe, they don't fly from a simpit either. Our real simulators allow us to change many aspects of the environment to suit the training/mission objectives. The lack of control and faulty logic is an issue easily resolved with giving control to the user.

I’d be happy with a simple command via the Comms menu to set lights to a few configurations and they stay like that until you change them. This way we can control the environment without random switching that doesn’t suit time of day, sun in the eye, weather etc.

Been a while since the last update, too busy flying! finally got the wiring for the remaining switches done, making the pit modular was a bonus as it makes it easy to pull down and access behind the panels without a major rebuild. DCS Bois is working well with just a couple of switches not quite doing what they should be doing. Now deciding if I want to do the right side panel (not in the original scope of a VR pit) and work out a solution for the gear and hook, also need to make a drop on cover for the foot well and rudder pedals to hide the ugliness of the back of the front panel, will probably go for a Alubond structure to keep it light weight. Also thinking of adding a canopy bow to make entering and exiting the pit a bit easier. it’s now become a major geek attraction in our house!

Ok I think I worked it out, It seems to be staying connected now. When I upgraded from the last Beta to 2.3.0.0 stable it ended up with both stable and beta installed. This has never been an issue before for me. I checked the export.lua and there was a double up of the simshaker entries, I've uninstalled the old beta and ran a repair on the export lua and it looks normal now. loaded my other third part entries and I think it's fixed. If not I'll report back after a DCS repair.

I have an issue with SSA dropping out during flight randomly, if I test the vibe motors on the jet pad they work fine, if I test the sound module it also works fine with my bass shakers. It just appears to be disconnected from DCS, if I shutdown and restart SSA it does not detect the loaded module. I have to restart DCS for it to connect. I have been using this config for a couple of years without issue, it appears to be something new either with DCS or SSA. I have reinstalled both SSA and the sound module, tried running them in admin. The disconnects are random and I can’t point to a single in game event. anyone seen this or have any ideas?

Yes it’s a DCS bug with the AI. It has been fixed for the next update.

Latest Moose.lua now has revised LSO handling for Spot 5 including new Sound files for LSO FF and Raynor. Sound Pack additional files attached to save downloading the whole pack. Airboss Soundpack spot 5 additions.zip

For those that want to build their own moose missions with the mighty USS America, my commits have now been accepted into the moose.lua on the latest release. https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/master/Moose_Include_Static Moose Airboss is now compatible with this cool mod. Happy landings!

Yeah sure you will need both mods as all three VSTOL carriers are in my testing mission. RaDG-Operation Saipan Arch II.miz

I have made an edited version of the moose.lua that includes the L61 Juan Carlos as an Airboss capable carrier, along with the new USS America LHA-6. Short video of it in use, setup at the moment to use spot 5 for landing, but this can be changed if needed. The videos I have seen has them using spot 5.

Ended up moving the Landing Coordinates a little forward 6 ft and it works very well now for landing just behind Spot 7. Quick video I did doing a run around the pattern with Airboss. Really looks great Admiral. Thanks again.

Looks pretty close for the Primary Landing spot, needs to come about 3 feet to port and maybe both the abeam landing stop and the primary landing spot need to move forward about 6-10 feet. Airboss use is totally acceptable as is though.

Yeah I sent it to Franky, they may choose to not add it as they are only supporting official carriers at the moment. I can also take my code back out of the moose.lua and put it in a seperate script that you load along with Moose to support individual Mod carriers? I’m also going to play around with the landing spot position and deck dimensions, but after a night of testing it’s pretty accurate as is, at least within the bounds of my landing abilities!

It's works fine, as long as you fly your approach 8m down the port side of the centerline to the hoverstop, Stabilise, then you will be cleared to land. You then cross to the tramline and land. The grading can be pretty harsh.

For anyone that wants to use the awesome USS America with Moose Airboss - I have an edited a personal version of the latest moose.lua that adds the carrier as an AIRBOSS capable carrier, It's based on the existing Tarawa (WIP) pattern settings contained in the script. It's becomes a standalone carrier throughout the script, so you can have both the USS Tarawa and the USS America in the same mission as two different airboss objects. PM me if you are interested.