Weegie

Schoolboy error sorted the roll, a rogue axis input no idea how, but it was on the rudder hence the roll That's sorted the Recovery and flying it now after the initial shock of stuff not working is not so bad. The other stuff still annoy's me though especially the fact I cannot raise the virtual seat and the borked instrument lighting. I appreciate there is not a module out there that's perfect BUT I reckon the Fishbed had got to be one of (& I strongly suspect THE) worst. Still cannot get Attitude Hold to work when I select it the jet either dives or climbs depending on the trim, Altitude or Recovery seems fine though. That said I still love this module, so much in it a real hands on cockpit Looking forward to the new cockpit, I just wish the Devs would give us some info or post some updated on progress Thanks to all for the assistance

Thanks for the replies it's appreciated I'll try it again, stupidity is not a factor that should be ruled out when I'm piloting If I still find it is behaving the same way I'll recoord some video and stick it up on YouTube to perhaps ellicit some ideas from the better informed in this forum

Perhaps it's just my stupidity but I have no clue what that is meant to mean When I was actually flying it yesterday, other things I noticed were a pretty horrid role that requires constant input to keep it level, worse when you envoke autopilot in "Recovery" it actually flies wing down and the attitude hold doesn't seem to work either, well not mine If anybody is not seeing these I'd appreciate input as then I know it's just me

Perhaps the external but the internal lighting is still mostly broke including all the axes controls The instrument lghting is also pretty horrible I'm not raging about it or going off on one. Seen that too often on the forum and it doesn't help anybody. I would welcome some news though on where the developers are with the new pit and what are the current plans I wouldn't even mind paying a little to get a new pit, because the time required to fix it must be significant and this is a business at the end of the day

So it's been a good while since I flew the Mig-21 It used to be my favourrate module and I love it So I made new profiles for a lot of stuff and spent some time then jumped into the cockpit Dear Oh Dear was I in for a shock or what so far not even off the ground and finding a shedload of really basic stuff totally borked, I'm not even able to adjust my virtual seat up I've heard there is a new cockpit coming, I do hope it's soon for me, as of right now the module is next to unusable I'm not going off on one but wondering how it could have been allowed to get this bad. I reckon it must be a very daunting task to make a module, let alone one as good as the Fishbed used to be, but borked instrument lighting and the seat adjust, kinda took my breath away Any info on when the new pit is arriving would be welcome

So glad that both Drakoz & SgtCyanide got at least a little something from the thread Makes me feel less guilty for all the time you guys spent leading a "newbie" by the nose Thanks Again Guys

Any skinners out there fancy knocking up a Sedish Tomcat? Similar to this one completed for the Hornet https://www.digitalcombatsimulator.c...files/3303014/ I'm a big fan of these camos, unfortunately like the idiot I am I originally posted this in the FA-18 sub forum

Oops was in a hurry & posted in the wrong section Perhaps a mod could move it to the F-14B Sorry

Drakoz Wow you are on a completely different level to me. Thank you so much for the thorough explanation and it will probably take me a few hours just to decipher some of this BUT I know it's going to be worth the time as I'll learn something from it and that's a lot of the fun I spend more time these days inside the TARGET Editor and Voice Attack than I do flying Your post is very much appreciated

Yeah the software isn't so easy, but jeez is it powerful. It has taken me a good deal of time to get my head around some of the basic stuff and now moving onto more avanced features. I've had a lot of problems with mismatches between firmware and the VKB_Joy, so I run a very old version Would I want it changed certainly not, it's a fantastic piece of software that exends the usage of the stick enormously. With my old version some things are quirky and some just don't work as described................So what, don't use them and move on Is there not a simpler version available anyway? Good grief when I started to use it there wasn't even an Englsh manual BUT I still love it and a significant amount of effort must have been made to develop it and I applaud VKB Really Loudly for doing so THANK YOU VKB

Any skinners out there fancy knocking up a Tomcat in the traditional Swedish Camo? Similar to this one completed for the Hornet https://www.digitalcombatsimulator.com/en/files/3303014/ I'm a big fan of these camos

Vaicom is a plug in to Voice Attack so you need to purchase both if you want to run Vaicom If you only fly the Horrnet you'd need Voice Attack & Vaicom.Obiously you don't need the Jester Voice pack & Chatter is an optional extra. Personally I'd start with Voice Attack and Vaicom & decide how much you like it. There is a free tester with Vaicom you can download to try it. If you like it then you can purchase the Pro pack with the additional features. Voice Attack will work without Vaicom but not the other way around. If you want you can also download some VA profiles for free, Bailey did some that permits you to control some parts of the jet via voice commands too. These packs that control some stuff in the jet can also be diasy chained with Vaicom so you can use both if you want

Sure guy's let me extract it from my VA command set and I'll either post it up directly here or as a link to DropBox Suggest you pop onto YouTube and watch in full screen if your interested to see the TACAN Channels Profile is in a zipped DropBox file here https://www.dropbox.com/s/evfs1q3r20my7iu/DCS%20F-14%20TACAN-Profile.zip?dl=0 Hope somebody gets some use out of it Apologies to Hollywood for the HiJack :smilewink:

I wrote a simple piece of VA code that I run on a seperate profile appended to Vaicom, it allows you to tune the TACAN in the pilot's pit separately. Rocket science it's not!! It works well if a bit slow but it's a good backup if Jester decides he doesn't can't be bothered. I have to call the command using VORTAC as opposed to TACAN as Vaicom takes charge if I use the word TACAN It also involves a reset at the begining to synch the TACAN channel in game to the Voice Attack (I'm no Hollywood) If anybody wanted it I could post it up

Gotcha I never thought of that, I already use flags to get the buttons to do different things when gear is down and flaps in various config, but never thought of doing that for the SHIFT key Thanks

Thank You Sir I tried your code on the APDIS same result, extremely flaky However I copied the original code I wrote for the APDIS to the joystick S3 button and it worked perfectly, so then tried the code on LDGH, worked as well. Then the Lightbulb glowed dimly into life Rather than use APDIS I'd try APENG............VOILA!!! All working exactly the way I wanted. Thank you so much for all the assistance, you've helped me enormously, very grateful for the advice and for opening my eyes into even more advanced coding

Will do & thanks again Well like I said the code compiled and the first short press would give me a 3 second shift actuation, after that it would just toggle. The sequenced long press worked fine, I'm not sure if it has something to do with the LED commands. I tried omitting the virtual shift code but even just trying to get the LEDs to sequence would not work. Exactly the same result, the short shift function would work first try (holding the shift for 3 seconds and then releasing) but subsequent presses just seemed to randomly light the LEDs. Ok just tried your code and it's doing something similar if not the same, I don't doubt you and I'm grateful for the assistance. I'm starting to think there is something else in the program code that's throwing it out and stopping it from working correctly. Later I'll try the code on it's own in a simple profile and see if it works there Once again many thanks for the help

I thought I'd try to be clever with the code but failed. I was thinking that I could introduce a TEMPO command so that a short press would give me a pulse on for 3 seconds then a long press would toggle the function (1st long press would turn on the "SHIFT" 2nd long press switch it off) When I tried that the first time run the code for a short press will give me the 3 second pulsed shift but subsequent short presses don't. If I map of each of the functions to separate buttons I can have a delayed pulse and a toggle but can't get it to work with the TEMPO. The second long line is the CHAINed 3 second delay, the bottom 2 are the the CHAINed commands I sequence with a long press. TARGET Scripting is fun but frustrating at the same time MapKey (&Throttle, APDIS, TEMPO(CHAIN(EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), LED(&Throttle,LED_ONOFF, LED_CURRENT+LED2),D(3000),EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"),LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)), SEQ(CHAIN(EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"),LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2)), CHAIN(EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"),LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2))),500));

Do you have the Options choice ticked in the Preferences section in Vaicom? L_CTRL/L_ALT/"C" Brings up the Vaicom window click on the Preferences Tab & in there is an "Allow Options" make sure that is ticked and it should bring it up in the game

So just to close this out. I copied the code and originally it wasn't working until I noticed it was configured for an F-18 Stick. After deleting the references to the F-18, it works a treat. Thanks again to Sgt Coyle for altering the script and to Drakoz for for his original code, I would never have managed this myself and its opened a whole new set of commands that I can use with the DefEventHandler

Wow Thank you Sgt Coyle & Thank You Drakoz I'll certainly read that thread too as it looks very interesting You have made my day Sir :worthy:

Hi SGT Coyle I'm struggling to think how I could better explain what I want to do. I use the APDIS swtich to activate the "SHIFT" mode When referring to "SHIFT" I mean this command SetShiftButton(&Throttle, APDIS, &Throttle, APPAT, APALT, IOTOGGLE); So the SHIFT key is operated by APDIS and toggles at the moment. What I was wanting was a way to enable the SHIFT function for a fixed time (say 3 seconds) then it would toggle itself off automatically, as opposed to having to give it another press to disable the SHIFT function

So I'm new to scripting and pretty green at it, so go easy on me. TARGET gives you the Upper,Middle,Down & Shift Commands to set up to 6 functions onto one button. I was thinking that what I'd like to be able to do is rather than have the "Shift" Toggle or Pulse it would be great if I could hold it down for a set delay, maybe 3-5 seconds then release. This way I could hit the button I have allocated to "Shift" then the button I want to operate when shifted. After that the "Shift" would then switch itself off. However as of now I can see ways to easily do that with Dx buttons or Keyboard comands but not with the physical buttons on the throttle. I do not even know if it's possible but thought I'd ask

Not quite sure if I'n following but, have you checked in the VA (not the VAICOM) setup that the throttle is mapped to VA? If it's not VAICOM Won't see it If it is you should be able to map the buttons to the throttle using the VAICOM profile PTT Keys. If that isn't working for whatever reason you could possibly set it up using the throttle to issue keyboard strokes, then using the same strokes set them up in VA. That would mean using TARGET GUI or preferably Editor and a lot don't want to do that (although it works well for me)

Thanks Drakoz I agree with all you said too that is also sound advice. If I'm having problems I usually set it for around 100-200 but even that may not be necessary. I've never really experimented so much I just siad 500 to make sure it did the job but you are right it does not need to be nearly so long Sort of academic to me though as I now script, the scripts unlock a whole new level of functionality and features. That said starting to learn to script is a real PIA as the syntax is pretty finicky. Should you change you mind to give scripting a try the best way IMHO is to read about some of the features in the Guide to scrpiting then make a base profile in the GUI. Run that then pull that script into the editor and hack away. Remember to save it elsewhere or at least rename otherwise the next time you run the GUI it wll overwrite the editor script (and all your changes)