D3adCy11nd3r

Took 8 days to get a reply but, Looks like EVERYONE who has vaicom needs to dig up their activation keys and put them somewhere off PC [A thumb drive perhaps.] "Hi there Thanks for contacting us. Our customers are advised to store their license keys in a secure location where they can be retrieved in the future. For reasons of data security and piracy prevention we cannot provide retrieval services for lost keys. All the best, The VAICOM PRO team" They had retrieved them in the past, No longer. Software is good and not extremely expensive so I will be buying license keys again. Just a bit aggravating since there is no "account" to log into and I have had vaicom for YEARS at this point, so those keys are long gone. Thanks for replying eventually though.

Emailed a week or better ago, no one seems to be monitoring the support account or they are back way up.

I have been using the mouse indicator locked to the headset as the reference point to do the bore sight and that has been taking care of the offset. Seems anything but right eye only has this issue. Honestly not even sure if it is a bug or just that since the source of the video is different it lines up with the IHADSS differently. [Which I guess would be bug like since it is unrealistic for the feed to be in the other eye to start with.]

Is there a way to change the location of the default carriers on the PG?

Did you make sure to do the mission script edit?

The RWR devices in the clickable.lua do not match the RWR in the input.lua [aka if you bind a key to the RWR power for example, it will not work.] To work around this [the dirty way] you have to get the device id from the clickable and replace it in the default.lua file. but it does create a duplicate input. Also there is not a D/L device id in the clickable that I have found so no way to even build this input.

I am missing one command after the update, not sure what it is but I have done the editor test/update multiple times and it always returns a missing command. Any ideas??

I am having a desync issue with rioai and jester in the F-14. When I ask jester to go standby, then have him do anything with the radar [easiest is scan range - ] then have him go active again he acknowledges the command and then proceeds to do nothing. Sorry if this has been covered before just makes nose cold fighting difficult to keep track of.

Alright, this may have aldready been covered but is there anyway to have jester control the radar when in standby mode without making it break. I.E if I go standby then scan range 25 it seems it pulls from the wrong menu and never recovers.

Perfect thanks man. Guess I will wait for a failure to hit. Thanks for hiding them as well, makes it even more unknown.

Well thank him too. The random failures do not seem to be generated however. it should show the failures in the sortie gen right?

@Miguel21 & @PB0_CEF you two are amazing, now if only ED would implement this system into the actual game and give you both a fat check for your efforts. and Miguel, thanks for the random failures being added in as well.

Probably when he releases the 11.0.8 versions. Besides IDK how much good it will do with the state of the viper atm.

Ensure you have updated to 11.0.7. Then request taxi [ignore the hold command.] Swing to the right [so into your wing man] and taxi to cat 1, that almost always works for me [unless there is an aircraft coming in to land.

Double click the firstmission file. It will open a prompt that will ask for a few inputs of what kind of mission. once generation is complete hit restart campaign inside of dcs campaigns and test.