Jump to content

Weegie

Members
  • Posts

    1124
  • Joined

  • Last visited

Everything posted by Weegie

  1. Yeah or/and possibly Amazon sending out stuff that's been returned by others, which they seem to be getting a reputation for. This is quite a common problem I reckon so TM should be more that aware of it.
  2. I have no clue as I've never tried to run VA twice. I'm curious what's wrong with appending your other profiles to the Vaicom profile, why the need to run VA twice, it sounds pretty complex
  3. Weegie

    Go to alternate.. ?

    I've had something similar only on multiplayer which has Easy Comms on, as I don't use Easy Comms in SP I suppose that sorta explains it. What happened with me was AAR, I'd tune to the correct frequency, call the tanker and immediately the frequency changed so I ended up talking to the wrong tanker. Even if you put it back it just selected the wrong frequency again What I did was unticked "Instant Select" and ticked "Select Tunes Radio" Preferences in the Vaicom pop up. Using that setup I can use "Select" to tune the radio if I want, but the main thing is no more frequency hopping with the radios
  4. Weegie

    Go to alternate.. ?

    I don't know but "go to alternate" is usually when the tower is too busy and telling you to divert to your alternate or divert field, could be a bug
  5. You talking about PTT bindings for the radio channels? I haven't tried it myself but I've got multiple commands in VA operating duplicate functions from different hardware and never had a problem Cannot see any reason why Vaicom would be any different, just duplicate the PTTs in the Vaicom profile and re-assign the new ones to the different throttle. You'll need both throttles identified as "joysticks" in the VA setup but as VA can support up to 4 it should be fine.
  6. Thank you @Smashy very helpful, I knew that .miz were just .zip files and that there is a correlation between trk and miz files, but thank you for going to the trouble and all the other info is very useful A little off topic but I think that from a .trk file you can actually recreate the mission fille, although quite how you go about it I'm not sure, I've never felt the need to do it.
  7. They're showing on my PC Try this https://photos.app.goo.gl/GuEPWH2ir6DuykQi9 & https://photos.app.goo.gl/LqSJQFSRxD58PiJ56 Are you saying the words aren't in your Keywords in the Editor? If they aren't then that would explain it. If they are in the Keyword but not in the VA Vaicom profile try hitting Finish on the Editor that should paste all the keywords in the Database to the Clipboard then follow the instructions to insert them into the profile
  8. There have been others having problems with navigating the tabs and opening the kneeboard, if that's what you're referring to. If I understand you can see the page and I'm guessing that you're trying to open the kneeboard using the embedded Vaicom command "kneeboard" and nothing happens then using the Vaicom commands to select the tabs. This seems to be a recurring problem for some and not for others. First check to see the command is being recognized by Voice Attack by checking in the Voice Attack command window. That will show you if Voice Attack understands the commands and is passing them through to Vaicom. I'm pretty certain this will be happening but check it anyway. A propsed workaround would be to try placing commands into the Voice Attack Vaicom profile to navigate the tabs. How to do this is explained on page 46 of the manual. In there Holllywood suggests that it's used for joystick buttons or keyboard keys. However you can also use it as a voice activated command instead, depending on what you want to do. As I'm using VSPX this is the method I'm using, there are/were some problems with tab activation when using VSPX and trying to call the kneeboard internally from the embedded Vaicom commands, so I'd try to make "external" commands as explained in the manual for navigating the tabs first and see if it works. I know you may not be running VSPX, but using a command within the profile seemed to have worked for some people (but not all) who experienced this problem If it does then perhaps another workaround for opening the kneeboard at the interactive page might be (depending on the module) to make a keybind for one of the keyboard commands that can jump to a shortcut on the kneeboard. Make that into a voice command to open the kneeboard at the Interactive page. I haven't actually tried that myself though as I'm running my own profile that pages to various sheets by counting up or down the kneeboard so I don't need to do that. If you are having problems making the commands, I have no idea of your skills (some are way more competent than me with Voice Attack, others don't know where to start) post again and I'll try to help you with the commands for paging through the tabs Although in the picture below the commands are marked voice disabled, that's because I'm using my own profile to activate the Interactive kneeboard tabs, which is appended to the Vaicom profile. When you make the commands make them voice activated to try them out
  9. Are you running as Admin? Are you using VSPX? Do you have Extended Command Set Option ticked (I'm unsure if this is really necessary or not) When you say it's not working, what exactly are you experiencing, when you page through the kneeboard do you see the Interactive Kneeboard Page with it's associated Yellow sticker and the tabs, or just white page or nothing at all? Others have had problems with Tab selection but AFAIK I haven't heard of anybody not getting it ro register at all (except if it's not registered.) If I use another profile without Vaicom running I see a blank white page where the Interactive kneeboard page is
  10. Weegie

    JF-17?

    That took me a little longer than I thought as I had to make some adjustements and improvements (I hope). The frequencies have been updated in the Gulf after all the changes made by ED a few weeks back. So (hopefully) everything works The profile only covers comms, so not in the same league as Bailey's but it's attached if you want to use it. Any problems or questions just drop me a PM JF-17 Comms-Profile.zip
  11. Weegie

    JF-17?

    @epolta yeah it forms part of my (very slim) VA profile for the Jeff that I append to Vaicom. I try to do this for the modules I've got, but it should be easy enough just to edit the list for the fequencies only and then export it to a separate file. It will just be a .vap file, with the airbases and another few commands radio commands (you might as well take that too). Pick 'n mix the commands you want or don't want and either use the profile as is or copy the commands into your own profile etc: etc: The programming would probably cause a coder to breakdown and weep (and not in a good way) I'm sure if @Bailey has written a profile for the Jeff, it would do something similar (and a lot more) Just use it as you see fit and for whatever purpose you have in mind. Should be able to post it up here later today
  12. Weegie

    JF-17?

    @epolta I don't know if it would help you or not, I have all the airbase frequencies I could find for Caucasus, Nevada, Syria and Gulf. I then made separate commands so as I could call an airbase in either UHF or VHF. These are all in my appended/piggybacked profile which I run on the back of Vaicom. What the commands do are manually tune the relevant airbase. It's really just the same command repeated 90 times but with different frequencies There is nothing special or clever about the programming, but if you want them or think they might help I'd pass them on, there are around 90 for UHF and the same for VHF. I use them more often than the Vaicom "Select" or looking up the relevant channel on the kneeboard. Using the exposed vairiable command for Theater (I think it is) the commands for a relevant airbase will only work if you're in that map. If you called it by mistake (ot VA misheard you) then you'd see it on the VA commands window but the command wouldn't be executed as it uses an "IF" statement to determine that he airbase is relevant to the theater you're flying in.
  13. Thank you @deltawhisky7 Great tutorial and very generous of you to take the time and trouble to not only give us a part but a nice pictorial guide on how to install
  14. I'm rubbish and only a simm pilot, so have nothing much to add. I find the Spitfire fine and perfectly stable after triming, landing is a bit tricky, what I do is try to hold it level or nearly level with some power applied. Seems to work nearly all the time. I find the 109 much more of a challenge to takeoff, fly and get down straight. When it was originally launched, the flight model was even more twitchy, but I think its been dialled down a little and the 109 tailwheel friction reduced making it more difficult. I'm using a VKB FBM stick with an extension. Flying without an extension though is whole different ball game, that could easily render it next to unflyable. Can you alter axis rates with your stick, like both the VKB and Thrustmaster Hog can? Reducing the virtual to physical movment might be a place to start to see if you can just fly circuits, then take it from there. Just a thought, I personally enjoy the Spit and fly it quite often
  15. Oh nice explanations @scoobie thanks Going to try that, before I've had full stick back. The auto prop controller which is trying to match RPM to prop pitch (KommandoGerrat or something) is very slow, this causes the pitch to vary and hence the torque applied, so you end up trying to counter, with rudder, a swing rate that's a moving target. Its like a PIO but with your feet rather than your hands I also switch it off and I read on here somewhere that a lot of the Luftwaffe pilots did the same. Problem was forget to switch it back and you're going to have a dead engine pretty quickly
  16. Question and if its ben already mentioned forgive me I did not read through the whole thread. I recently went back to the 109 after a long time away, spending time in the Spit instead. Well I see ED decreased tailwheel friction, or perhaps all tyre friction, unsure, anyway the 109 was a beast, especially landing but take offs were pretty exciting too. To my question, I normally have trim full nose heavy and when using that in SP its been fine. However I went onto the Aerobatics server and did the same thing and got launched waaaaay earlier, almost like no trim was applied. I checked on the dial and defo full nose down but it didn't seem to behave that way. Am I imagining it, becuase I felt there was a profound difference? Trimmed for landing although I normally have around 0 to -1 trim in at landing anyway and it was fine
  17. @amazingme approach speed is 200 on the threshold, touchdown is typically 160-150kph. I've tried various trims between 0 to -2 and IMHO apart from stick position, it doesn't appear to me to make a great deal of difference. Usually I try it with 50% fuel loadout and no extra stores Both you and @razo+r are suggesting a slightly higher approach and possibly touchdown speed at 180 than I'm using so I'll try that I also noticed that I was using an old gash mission, I made a new one for doing circuits and it seems to be an improvement, don't ask me how but I've noticed this before with other modules that old missions seem somehow to affect the flight model. I now seem to have more rudder control on touchdown and although still seeing the swing, its a lot easier to counter with a boot full of rudder. Thanks the suggestions are appreciated
  18. I've came back to the 109 after a long time, mainly spending time in the Spit (as well as the jets) I used to think the Spit was the hardest of the warbirds to land (& takeoff) satisfactorily, but rapidly changing my mind. The 109 is a bit of a beast, I'm unsure if its changed or it's just me. I can get it down crossing the threshold usually with a little power applied at around 200kph levelling out and keeping the nose level or slightly high as the speed decays and let the aircraft settle at around 160-150, pulling the stick back after the gear touches down. I've used this approach with and without (a little) throttle applied, dead straight and everything lined up. It touches down gently and all seems to be going well However when I pull the stick back I nearly always get a severe swing usually to the right, which I don't understand. I gently touchdown, I'm straight and no change in power so why does the aircraft develop this swing? In general it feels to me like the friction of tyres to runway has been reduced since I last visited the module. Despite the locked tailwheel the 109 is every bit as twitchy as the Spitfire I reckon, despite the Spit having it's tailwheel semi free (the Spit has a lock of sorts as I understand, that keeps the tailwheel straight unless a distinct turning moment is applied to force it to castor). I looked back on some older video I have of landings and noticed previously that once lined up and after touchdown, no rudder changes applied, providing the touchdown was straight and gentle and no power changes it tracked straight with little to no directional change. Not any more though!!! Any insight or how to stop it appreciated
  19. Nice, I'm a big VKB fanboy, love their stuff although the Configurator takes a little getting used to. That said once you start to figure it out, it's really powerful Have fun
  20. Thanks @sthompson I have a command that can select a profile dependent on the module but it requires to be exectuted and so far I've failed to automate it. It probably could e done using Hollywood's method or perhaps via a call using the DCS Bios to determine module type, but as I don't really need it to be automated I haven't done any more. It would be a nice to have though. I just use a series of "IF" statements to select the module based on Hollywood's exposed variables, I've also got a command that I use dependent on map as well, that uses the same methodolgy and I use to select relevant pages and airbase frequencies, via my own appended profile. So first what I have is multiple Vaicom profiles that are all identical except that each of these Vaicom profiles has appended (or piggybacked) onto them my own profile pertaining to a specific module. The Module Select Command interogates Vaicom using an exposed vairiable to determine which module is currently running, Voice Attack then selects that module. I've attached it, ingenious or clever it's not but it might give you some ideas, it won't work though unless you've got your VA/Vaicom profiles set up similar to mine. Link to a similar sort of thread is here, with some more inforamtion is here https://forums.eagle.ru/topic/254253-daisy-chained-profile-switching/?tab=comments#comment-4498209 Module Select-Profile.zip
  21. I doubt then that you're running VSPX, I'm not trying to be clever or sarcastic but have you had a look at the manual? The Vaicom manual is excellent, I wish other software providers went to as much trouble VSPX is an alternative method of speech input where you don't have to wait for the bleep after contacting a virtual aircraft or airfield before saying the command. You can tell if it's activated by looking at the Editor Tab on the VA pop up. To the left of the microphone symbol is a VSPX "light" if you have it enabled it will be green. You also need to have the Extended Command Set option ticked in the Preferences tab of the pop up for the Interactive Kneeboard to function corectly. When you say the Debug isn't showing anything odd, I'm assuming that you've got the "Run in debug mode" enabled under the Config tab on the pop up and it's not showing any problems either. That's about all I have, did you open the kneeboard through the keyboard and key to the Interactive Kneeboard page to see if it looks the same when you try that? If you're still having problems and you can't find a fix, as it sounds a strange problem and above what little troubleshooting skills I posses. I'd go to the Vaicom webpage and then drop Hollywood or one of his team the question. They have been very helpful to me in the past.
  22. Looks to me like he's moved the cockpit seat position. Remember that you can move the seat as well as zooming. When you move the seat you'll increase/decrease the size of HUD text. Combining Seat movement and zoom you can get the size of cockpit view you want and also get the HUD text to still be seen. Be nice if @Biga42 came back to confirm but that's what I use when something similar happens and have these commands bound onto my hat that I use for changing views
  23. I wanted to set up some controls on StreamDeck for the MiG-19 but although listed in Ctyler's excellent tool nothing seems to work and I noticed there is no Export.lua for it. I'm ASS-uming that's the reason it doesn't work. If I'm wrong feel free to educate me So I've seen Export.luas being made by copying another module's Export.lua and then editing it to suit. Was wondering if anybody had an Export.lua for the Mig-19 or could perhaps help me create one, I also posted up in the relevant module forum too but thought I'd try the Scatter Gun approach too
  24. Ok perhaps it's just me being a sausage finger clutz but I tried to use Ctyler's StreamDeck tool with the MiG 19 and although I can see a bunch of commands I'm guessing from ClickableData.lua but not sure However there is no export script that I've found for this module and with quite a few things that I can't do from the standard input file in DCS I was hoping that I could use the StreamDeck. The upshot is nothing works and it doesn't appear to communicate with the StreamDeck. The problem appears to be that it's just not a popular module, which is a shame as visually I think the cockpit is really nice, but the idea of having to click around with the mouse it just an utter pain. Is an export script in the works for this module?
  25. Well that answers that, it all looks good. I assume the opacity slider is turned up (I know that's sorta silly but it's the sorta dumb assed thing I'd do) Are you running VSPX (I am so need separate commands made into the Vaicom profile) Have you tried opening the Kneeboard with the keypresses, I think it's R_Shift K, then using your square brackets to page to the Interactive kneeboard to see if it still looks the same? From the commands in the Vaicom window it looks like Vaicom is waiting for something else to be said, as if the command is not complete, which is odd. I doubt I can help much more as I run VSPX and it's known that there are some problems with the internally generated command set when using it, but I'll take a look and if I see anything I'll post back up
×
×
  • Create New...