j9murphy

The only options I have are "Clamp" and "Allow" for LOD Bias?

I do have a variable power supply on my electronics bench that I could use to find the optimum value. It would also tell me how many amps the seat is drawing at any given time to provide some guidance there. I dont have the time to do all that today or tomorrow, but maybe towards the end of the week I could experiment and see what results I get.

Thanks for that tip! I've been struggling with the same issue. I prefer most of the effects to be rather subtle (especially engines and the low end of the g's), and every time i turned them down they just disappeared or didnt work properly. I 've ordered a new adapter from Amazon, hopefully that will fix the issue.

It did seem to correlate to that timeline wise, however I have since removed both the open beta and release versions of DCS and only reinstalled the release version...

no effect:(

I tried uninstalling DCS, removing both the install and saved games directories and reinstalling, still no joy:( I'm really not sure what else to try, it used to work fine:(

Anyone know what causes this in the kneeboard? All the tabs are empty and I cant switch between them. Entire kneeboard is faded out. All other features of vaicompro including other kneeboard pages work fine though. It's not the brightness slider in the control panel, and I've repaired and cleaned everything... no clues in the log file. Any ideas? (DCS Relase Version and running VA as admin)

I'm having problems with the kneeboard in the f18. PTT works and the sim responds to commands, but when I bring up the kneeboard all the the vaicompro tabs on the page are empty. All other pages display fine. I reran the vaicompro setup and selected repair, which didnt help. I'm using the latest release version not 2.7, although I do have 2.7 installed. Anyone else see/solve this?

Did you really mean 4,000 for preload radius or 40,000?

I'm sure this is somewhere in this thread, I've just been unable to locate it... How do you make VAICOM work with 2 separate installs of DCS (stable & beta)? the export.lua is correct and the VAICOMPRO directory is in the Scripts directory of both. It is working in my first install, just not in the second. Thanks for pointing me in the right direction....

Exactly, specifically the render mask. Is there a mod for a render mask out there that would work with this?

I can confirm that works very well with the Odyssey Plus headset:) I'm using these settings from the post above.. Is there someway to add the mod that changes shape of the windows being drawn for VR? PreprocessorDefinitions= Techniques=VRSharpenColor@VR_CAS_Color.fx TechniqueSorting=VRSharpenColor@VR_CAS_Color.fx [VR_CAS_Color.fx] Brightness=0.985000 CASContrast=0.600000 Contrast=1.00100 MaxDelta=0.100000 Saturation=1.100000 Sharpening=1.700000

Thank you for the response, one more question. Can I unzip the seat and change the exit of the wires to the other side without creating any problems?

Accidentally posted this in the wrong thread, moving it this one... Got my jetseat yesterday evening, thanks for that! Arrived pretty quickly. Have a couple of questions based on configuring last night for the f18.... - what is the proper procedure after you make a change in one of the settings in simshaker for aviators for that change to be recognized? Turning the effect on and off seemed to be recognized immediately, whereas changes to the intensity value seemed not to be applied immediately. Do I have to restart the mission or the seat or both or? - several of the effects seemed to have a minimum intensity value in SSA for them to work at all. For example, I couldn't get any feedback at all if the canopy open/close was set for less than 15. Should I be able to feel small values all the way down to 1? - what do the filter options do on the Special Options menu in SSA? Thanks for you help!

Got my jetseat yesterday evening, thanks for that! Arrived pretty quickly. Have a couple of questions based on configuring last night for the f18.... - what is the proper procedure after you make a change in one of the settings in simshaker for aviators for that change to be recognized? Turning the effect on and off seemed to be recognized immediately, whereas changes to the intensity value seemed not to be applied immediately. Do I have to restart the mission or the seat or both or? - several of the effects seemed to have a minimum intensity value in SSA for them to work at all. For example, I couldn't get any feedback at all if the canopy open/close was set for less than 15. Should I be able to feel small values all the way down to 1? - what do the filter options do on the Special Options menu in SSA? Thanks for you help!

My throttle has an idle/off detent as well so I have some X axis saturation dialed in to prevent the throttle from spinning up until after that detent. The axis is also inverted. Is there a way to still use the excel sheet for the after burner detent?

in case the helios developers want to support the knobster, the code is here... https://github.com/SimInnovations/libknobster

I sent him an email will let you know when I get a reply. It's an Arduino Nano device if that helps at all. It's connected this way... Rotary encoder pin - Arduino Nano pin Inner encoder A - D4 Inner encoder B - D5 Outer encoder A - D3 Outer encoder B - D2 Push button - D6

Assume you saw the video demonstration... works very well. I've exchanged emails with the creator before, If you like I can ask him if he has or would be willing to provide an api that could be used with helios.

Any chance the helios authors could add support for this? https://www.siminnovations.com/hardware/product/57-knobster It's a rotary dial for touch interfaces. I use it in Xplane and it really helps make touch interfaces much easier to use. I use a 24" touch panel below my main monitors for helios in DCS and AirManager in Xplane and love the way it works.

Just found out this is an open beta feature only which is why I wasn't seeing it.

**** solution found. I added registry key/values for the stable version: HKEY_CURRENT_USER\Software\Eagle Dynamics\DCS World\Path and now Vaicom finds the installation.

I'm getting a message in voice attack: "7:48:35.821 DCS World version 2.5 not found." the registry entry HKEY_CURRENT_USER\Software\Eagle Dynamics\ only has entries for openbeta, there is no entry for the sable version. could someone post what the key names are for the stable version, and I can try and put those in to see if vaicom finds it then?

I checked the OB box and restarted, but it still only creates the files in the open beta install and not in the stable install....

I have both open beta and stable installed. I checked the open beta scripts directory and that's where everything went. I have vaicompro custom configured for stable, and did *not* check ob. Why is is still going to open beta and not the stable release?