Weegie

Ok Narrowing in on this, after some more experimentation I've found that if I run Vaicom stand alone it all works. I normally have a second profile piggybacked, when I select that I get the problem. Going to investigate and go through the piggybacked profile for possible conflicts and report back

MAX Thanks for the reply appreciated. The "Allow Other Commands to Execute While This One is Running" is checked for all my PTTs and they are all correctly configured for the Execute Pressed & the Execute Released, with the Released button having the Option "Only Execute When Button Released" marked as appropriate. When I force a "Stop All Running Commands", nothing is indicated as running in the VA dialouge. For the Second issue Yes you understand it perfectly, that's the problem and the button is confiigured exactly as the other 5 are, which do register in the PTT Window, but the AUX does not. The other thing I notice, when using the virtual button on the Vaicom PTT page the Relay light illuminates. When I use the button on either throttle is doesn't. I have all my PTTs configured with a button and a keyboard command (seperately of course) operating on 2 different throttles. Using either I get exactly the same behaviour and all other PTT commmands work exactly as they should. So I'm pretty certain it's a Vaicom problem. I've reset the lua's in Reset, no effect. Wondering now if I should try a clean reinstall

Constantly getting Command canceled: Another command is not allowing others to execute (canceled: Transmit TX6 press). In VA Window when I press button 6 on my throttle designated tthe AUX Channel Checked Vaicom PTT button and everything Ok No mention of anything abnormal in log AUX does not show in PTT Vaicom Page "Screen" and I only get AUX in there if I use the TX6 AUX Button on the PTT Page Everything elese seems to be behaving for now Any ideas or anybody getting the same?

Hi TOViper I posted as it drove me nuts and I thought if anybody else was having an issue it might help them to a quicker solution. I love the Viggen, it's brilliant both in the aircaft design and Heatblur's implementation, the Radar is a work of art :thumbup: However there are a lot of outstanding issues that have been present since it came out that haven't been addressed. One more thing on the settings. A lot of throttle movement is required to start the engine spooling up and when it does it accelerates like a scalded cat on the taxiway. For me this results in initially a large throttle movement, then back off to a minimum, eventually freewheeling at idle followed by further bursts of throttle. To help with that I set the throttle Y saturation to 92% on my throttle, so the slightest throttle movement gets the virtual throttle off the stops and makes it much easier to use. Others may differ depending on their hardware but taking the excess movement out the throttle made it a lot more pleasurable for me to taxi around.

Probably the fact that the Throttle and Start Up Panel come in on 2 different USBs so Windows assigns them as 2 devices. If assigning switches the Start Up panel needs to be used not the throttle That one "got me" too for a little while

I can only partly answer, probably like most you've invested a lot of time on profiles for devices, they aren't lost if their order or hardware id's change. What to do is to copy and save the Config\Input folder somwhere out of the Saved Games\DCS folders. After say a worse case Windows reinstall open DCS with all your devices enabled then close it. DCS will make new profiles for the devices with the new addresses that Windows has now assigned them. Copy the filenames of the new devices in the SavedGames\DCS\Config\Input"Aircraft" directory, one at a time. Then assign that filename to the saved same device in the Input folder that you moved elsewhere. You can now take that renamed old file (containing all your settings) and put it into the Saved\Games\Config\Input"Aircraft" directory replacing the file that was there perviously. Alternatively you can open the old saved input content in say Notepad++ and copy the content over to the new device file that DCS has made. It's still a bit of a faff to do but it's better than having to redo all the control bindings. On an aside I think that when there have been changes to a modules settings file in the game via an update, the settings revert to default. Your old configs are still there, but the problem is if you don't check and exit the game without loading the setup files that were there before the update, then the default settings overwrite your previous ones. Resulting in a loss of the settings. I'm still not 100% on this but I think that's what happens. What I'm doing now is saving my input files outside the Saved Games/DCS folder to somewhere else just in case at every update. I've recently seen this happen not only to me but a few others with the P-47 and it's an almighty pain

This really had me totally foxed up until a few hours ago, although I was up against 2 problems, the first was how to make any sense of what the Axis Controls Window was trying to tell me and the second was the Viggen brakes axes. After I finally figured what the window was telling me I still find it far from intuitive and couldn't find a definitve explanation anywhere. It could be made so much simpler to understand than it currently is, but I digress Next the Viggen brakes were vicious, far too sensitive, so I placed the Y saturation at 50%. The setup with my rudders meant the inverted and slider boxes were both ticked. I also had a curvature of 25 diallled in. I could not understand how the brakes were still super sensitive one tap throwing the thing to the left or right. After more experimentation and a buddy telling me to use the controls on screen indicator the penny finally dropped. When the inverted box is ticked in the Viggen with the Y saturation at 50% what you get is not 0-50% on the virutal axis but 50-100% Here is a shot of the Controls indicator in game the LH pedal is inverted, both feet off the pedals Here is the inverted axis tune for the Viggen Here is the same sort of setup on the Hornet (with this my axes are set to the opposite of the Viggen) so theoretically it's the same setup. You can also see that the curvature should now be set negative, which makes sense as the axis is inverted By inverting my pedals using the software supplied with them and unchecking the inverted box I now have a reallly nice setup, but good grief I did not expect different modules to behave differently when you give them the same settings, from the setting options :doh:

Thanks for coming back with some stuff to try I'll give these a go and report back. I did see that you can either let Vaicom control the PTT or use "switch" as an option in the settings

It's no solution, but I was trying to get this to work as well and just found it a bit haphazard. I didn't want to be screaming commands meant for VA or Vaicom into a channel populated with other players (especially on GUARD) After testing it several times I gave up. Now I have my radio selection as my PTT for Vaicom, so I can tune the radio then talk to VA/Vaicom, this also of course sets the frequency for SRS. However my SRS PTT is on another button, so if I want to talk to human players I need to press that. That way Vaicom/VA is completely seperate from SRS. For me it works pretty well & I'm more comfortable that I'm not that idiot blocking the frequency. Plenty of IRL examples of it too, so the pros get it wrong as well.

Good idea too Supmua................if it works it works Cheers

Really like the Mirage, but I hate using the clickable cockpit unless I have to preferring to use keybinds, or my StreamDeck using Cytler's awesome software, if the keybinds I want aren't avaialable I'm having a lot of problems with the Mirage, the Keybinds file is pretty poor IMHO (bit of a Razbam weaknness) and it seems that there are bugs in the export.lua (not sure who made this or if Razbam made an official one) I read a while back that more effort was being put into improving the Keybinds file. For me it's a big weakness in the otherwise great Razbam modules and I'd love to see some improvement, is the keybind file still getting attention? At least with the new radio I can now talk to the Towers using exports via the StreamDeck and tune the TACAN, which is a big step in the right direction. Apologies if this sounds like a moan or rant, I don't mean it that way but it seems that Razbam assume everybody uses the clickable cockpits

Milou Yes I could do that but I'd lose around 25% of throttle range, by that I mean the physical movement and I wouldn't want to do that. I'd also need to recalibrate every time I wanted to use the fingerlifts and I try to mess with cals and firmware as little as possible. The response is appreciated though. streakeagle, that sounds llike an idea definately worth exploring and thanks for suggesting, I'll be looking into that.

Thank you so much Shu77, that's super That answers my question (I hope) I'll mess with it later today. Yeah it was the throttle backlight I was referring to as opposed to the MFDs (which I don't have.........YET)

Just to chime in I'm totally in agreement MustangSally The throttles are great, apart from the friction control being an axis, which is really stupid IMHO, so I don't use the axis either. Yet to mess with the Neutral Feel tension control on the main box itself though (don't understand the instructions and just haven't felt the need). I installed the throttle "spacers" from the get go and don't have any issues with the throttles interfering with each other, some early version reviewers complained about. I don't use the software at all it does appear web based. The Dx buttons also have positions for Off as well as On making it super easy to configure. For any keyboard commands I want to use as opposed to Dx I just run them through Voice Attack. This lets me synchronize with TARGET on the Hog throttle with the Super Taurus if you want to extend the use of switches for "Shift", "Modes", "Tempo" etc: My only gripe is I wish the Finger Lifts could be locked up in order to advance the throttle thorugh its full range without activating them, for the warbirds or some way of removing the burner detent. You can push through them but I feel that's a bit coarse and not exactly sympathetic to the hardware. Overall so far I think they are great

Sweet looking forward to seeing it released Very cool

Looks Great Hollywood Thank You p.s. hope my request for an Exposed variable for the different maos hasn't been forgotten

Ahh missed that Thank You Hollywood that explains things. When I use finish though the airfields don't come into my Keywords in VA. Its not a biggie if it's coming along in the next update, I was just curious why it seemed to be in the Editor but won't import into the Keywords I tried manually adding Incirlik, just to see what would happen and it recognized the command and constructed the message. This was outside the game using the VA window to look at the returns. Going to try it in the game to see what happens later.

So did a fresh install of Vaicom and now the Syrian Airbases have disappeared from the Editor as well. I wonder if the Import Extended F10 menus had something to do with them being previously present in the Editor I'm getting the airbases recognized if I tune to the correct frequency but calling them using the airfield name does nothing and it appears their not present. My take is it's sort of implemented but not fully in as much as you can tune the radio frequency and get a response but not call them by name Would be nice if Hollywood would give us an update on the status, either here or on his webpage. I can't even find release notes for all the various versions

Mmmm Need to check some more I have the Syrian Airfields in the Editor but when I uploaded them to the Keywords they don't appear to be there. Gulf and Caucasus Airfileds (for example) are so is something not quite right Need to do some more checking Thanks for the replies

Is there an easy way to do this? I've been trawling some threads but the usual way is to set the intensity to "0" When that's implemented the LEDs don't turn on either It's possible to turn them off with the GUI but I wondered if anybody could assist with a script that would kill the backlighting but still keep the LEDs available to be turned on & off like the GUI can

I was having problems trying to contact the tower at Incerlik but that was as far as I got Just wondering if it was my accent or if Syria hasn't been incorporated yet If it's not any clues when an update is planned for? Thanks

Skunk...............long shot but you're ot running Windows 7 are you?

That's interesting never knew that I've had this issue fairly recently too. It came back but after a recal, certainly some sort of reset would be a lot easier to implement Given a few reporting this I'm starting to wonder if something has changed to cause this. Bloody Windows I'll wager TARGET can be a bit flaky for me as well, meaning I need to kill the stick and disconnect the USB. Reconnecting and restarting TARGET (Editor not GUI) brings it all back. I really Like TARGET but all this hassle is tiresome

My profiles do that to, I can't be 100% but put it down to the scan time and latency, depending on what interval you've set to request DCS to export and scan the state of the devices. If it's set low, I'm scanning at twice/sec this means that when you flip a switch if the export has not been scanned it'll be at the previous setting so the switch (or whatever device) will be in the old position, so the Streamdeck animation will move the device to that position. Once the export has been sent to Streamdeck and then been processed (which will also be a short interval) then the device will move to the correct setting

Thanks Ctyler I'll look into it a bit more, fantastic plug in thank you so much, that was the problem the Gun Safety wasn't monitored, it is now in my export.lua Now I'm struggling with the P-47 trying to switch the prop pitch from manual to auto, I think it's a similar sorta thing but even the rotary won't work, but thanks for that explanation it will help me troubleshoot that too. Of course I'm using an export kindly shared by another member on here, but there is something well wierd about that 4 way switch and the way it behaves. EDIT found the problem there too, the P-47 Export file is reporting 0.0 no matter the state of the switch. This is clearly amiss as setting up a button and sending a 0.3 value moves the switch but the export back is stating 0.0 Just have to wait for an official P-47 export file I guess Thanks that helped enormously