BaobobMiller

Hey Scott, I don't remember weather or not I mentioned it or not, but it would be extremely helpful if clicking save on a script (editor) or button assignment (joystick page) the it reloaded the LUA engine a second later (to give time for the file to save first). After an hour or so of working on a module it gets rather frustrating to have the extra step of switching to the settings page just to hit reload and then back again. Cheers, Bao

Hey guys, I'm trying to switch over to FSX-SE and I'm running into problems. Namely... everything works except LINDA. I'm using FSUIPC 4.939n and the default FSX-SE SimConnect (10.0.62613.0). I have thus far been unable to get LINDA to recognize that FSX-SE is running... (cant sync up) FSX Sync button remains blue and every time I click it it changes the aircraft drop-down menu back to "-- Aircrafts --". I was able (on several previous installs) to get it to work by installing the XPACK version of SimConnect from the LegacyInterfaces sub-folder in the SDK folder. However if I do that I my Flight1 GTN's crash the simulator after informing me that the SimConnect version is incompatible. Any Help? Ideas? Pointing and laughing? Thanks, Bao

All Versions after 2.5.7 (including 2.6.2) are still causing FSX to crash faulting ntdll.dll. Is there perhaps any way that we could get a version of 2.5.7 with the panel position saving put back in it? Thanks, Bao

I don't mean to suggest something that sounds like a no-brainer... but don't make the mistake I did and forget to re-run the VoxATC Indexer after installing the package. Any time you install a plane or scenery you have to run it to get VoxATC to recognize the changes. Took me days to figure out why I was being routed around planes that were not there... it was because I had not re-run the indexer. I ran it and they all showed up. Same goes for airports, and AI planes. By the same token any change you make to an aircraft.cfg or bgl file does not seem to be implemented until after the Indexer is re-run. Bao

Hmm... Where in the file did you put the entry? I added it and it worked great for me. I added it as the last entry so the tail end of my file looks like this: <ProcessorPriority Value="Normal" /> <TaxiPathLights Value="TRUE" /> <ExternalSidStarFolder Value="" /> <CommRetries Value="5" /> </Settings> Bao

I can not agree strongly enough. I do use the VoxPop voices as well (exclusively for other aircraft) but all my ATC's are Ivona as are a few of the Aircraft. I picked up some foreign voices with really thick accents from Ivona as well and assigned them to aircraft to help with the illusion of international pilots from around the world and I LOVE IT. Good Flying, Bao

...?... I don't understand the problem I guess... I just key up and say "Landmark 272 request flight level 240" or whatever altitude I need. I either get moved to that altitude or I get "Landmark 272, unable at this time. Bao

I must have missed that one too thanks Mike now if I can just find a parameter to increase the frequency of the METAR import to VoxATC... Bao

While I have had planes taxi through my tail section while I was calling for clearance, I have never encountered something as drastic as posted in the videos above. I would like to suggest if I may that the next time you see this kind of behavior you open task manager and check the processes tab (If you have not already). I have been doing a lot of reading in the forums lately and seen quite a few problems that could be explained by two VoxATC Server processes running at the same time. Two servers running simultaneously is something that happens to me every time FSX Crashes while VoxATC is running (Enabled). When FSX crashes VoxATC is not aware of the flight simulator closing since it was an abnormal shutdown. Upon restarting FSX, the VoxATC panel is not aware of the already running server process and starts a new one. If you couple that with the fact that VoxATC generates and controls its own AI Traffic you can end up with two sets of traffic fighting over the same airport. And then it gets really interesting. VoxATC takes snapshots of the weather METAR and uses them for "as long as it feels like". This is why people who use weather updates from programs like REX (like I do) find the AWOS reports to often times be inaccurate. For example if I start FSX, turn on VoxATC and tune to the AWOS frequency before REX injects the current weather, the snapshot that VoxATC has and is repeating to me is not the same as what FSX has for weather. I'm not sure how to get VoxATC to re-read the METAR from FSX but I do know that just flipping off the frequency and back again does not work. If it were me... I would call it a bug and change the code to update the METAR in VoxATC at the beginning of every loop of the "transmission". At any rate I just wanted to share my thoughts and see if it helps. if you do find that you have two processes running you can turn off the current one using the disable button from within FSX and then close the other one with task manager. After that just hit the enable buttim fron withing FSX to fire a clean copy back up. May your simulator flights be blessed with cloudy skies server wind sheering engine failures and damaged landing gear... and may your real flights be blessed with none of them. Bao

There is another condition that can cause the "Double ATC" and that is having VoxATC running twice. Sounds silly I know but it happens to me from time to time. You can't (to my knowledge) deliberately run the progeram twice but if FSX crashes while VoxATC is running, that instace of VoxATC continues to run in the background. After restarting FSX the VoxATC popup window does not see the already running process and offers you the "enable" button which starts a second instance of the program. This can cause several issues not the least of which is 2 atc's. generally it's easy to spot since on most cases one atc is acting normal and the other seems confused... "Last aircraft say again" for example. But not always. As for the weather being different from that displayed in the strip. VoxATC takes a metar "snapshot" and uses it for quite a while. if when rex injects weather fsx wil pick up on the changes right away but VoxATC continues to use it's "snapshot" not knowing that it is no longer valid. In my opinion the best long term solution would be for the developer to make the "AI" read the metar for the in range tuned weather station just prior to each "loop" of the announcement. In the mean time the only way I have gotten it to change is by disabling and re-enabling VoxATC which is seldom convenient. Good flying, Bao

I almost never use the "0" menu for anything. I just ask... and it usually works. For example: "Minneapolis Center, Landmark 272..." "Landmark 272, Minneapolis center... go ahead." "Request Flight level 240." "Landmark 272 Climb and maintain flight level 240" "Climb and maintain flight level 240, Landmark 272." Incorrect as it may be I have also been known to jump right in with... "Landmark 272 request flight level 240." as the initial radio contact. Cheers Bao

In addition to the parking issue I'm having, I am consistently having difficulty declaring an emergency. Aside from the frequent "unable at this time" which I assume has more to do with me getting used to telling VoxATC exactly what it wants to hear, I have the problem of being told to "immediately climb and maintain 5900" after declaring an engine failure in my single engine aircraft. I also notice that there is no option for multiple engine failure if that were the case. Any thoughts? Bao

I have seen a few posts arguing about gate assignments and weather or not to add lines to the aircraft.cfg file or not etc. What I have not seen are clear instructions on how to actually get it to work. I have seen things like... "make sure these two lines are properly filled out in your aircraft.cfg file..." which firstly leave me wondering things like, what section do they go in, because they are not there to fill out. My problem may be compounded by the face that I fly general aviation almost exclusively but I still need to be able to be routed to a ga gate or ramp or a fuel box rather than just being sent to the farthest possible corner of the parking area. cheers, Bao

Hello campers!! This post is to ask for multiple shift states as a feature request. How many of us have saitek flight controls with otherwise useless mode switches on them? I say useless not because they are exactly, but rather because most of us have been unable to do anything with them unless we use the saitek profile software and lets face it, for most of us that is just not good enough. It can tend to be unreliable, laggy, etc... not to mention it only sends keystrokes, and it doesn't even do that very well depending on the keys involved. But it's a great idea right? I know, some of you are still saying "What Idea?? I never could figure out what that thing is for!!". If you already know, great. but please keep reading anyway (I really am going somewhere with this). FIrst for those who don't yet know how the mode switch is supposed to work. The mode switch was designed to be used with the saitek profile software to allow you to assign the buttons on your controller (in my case the pro flight yoke) to more than one command. with the switch set to mode 1 for example my A1:A2 switch can be probrammed to Elevator Trim Up and Down while with the switch set to mode 2 it can be Camera Zoom in and out. Cool Right? Three modes essentially means 3 times as many "buttons" right there on the control wheel since they are ALL able to be set up with 3 commands each. The downsides of course incluse things like: you can only assign keyboard commands using the profile software (which means that thanks to Microsoft in their infinate wisdom leaving several vital commands OFF the list if keybindings that you can set up in game... you end up either modifying the keybindings manually in a text editor and hoping FSX doesn't overwrite the file with default values too often, or using yet another third party software such as FSUIPC to read the key combinations you programmed the profiler to send in order to listen for those fake keypresses and turn them into fsx commands. Is your head spinning yet? What if that wasn't the case? What if you could use your mode switch as a Shift state right in LIDNA? It would be easier... faster... and all your bindings could be in one place rather than having some in LINDA and some in a combination of the profile software and FSX while still others such as the Altimiter bug I keep set ti the mode 2 B1:B2 combination are set with a keypress being generated by the Saitek software and then using FSUIPC to translate that into an offset and pass it to FSX. Now for those who are a little more advanced you CAN just upen up the FSUIPC.ini file and write yourself a few complex button assignments... Something like n=CR(+0,10)0,5,C65892,0 but isn't the reason we are using LINDA really to make things easier and to consolidate our control programming? For thise of you who are advanced enough to feel good about adding complex buttons to the FSUIPC.ini file.... GO FOR IT!! no really... You can have full use of you mode switch as soon as you do... and as soon as you read the rest of this post and follow an instruction I'm going to give to the rest of the community. For the rest of you, the fact is... I can get you half way there. The other half is going to have to be added byt the LINDA developers directly. FIrst, (and I know this may make a few of you uneasy) as most of us know saitek wrote the drivers for their controller software to deliberately hide the mode switch from everything except their profile siftware so that you could not mistakenly try to program in game functions to the mode switch... so we have to undo that... It is actually a function of the profile software itself. any thime a profile is loaded the mode switch is hiden. What's that you say? You don't have a profile loaded? Well actually... if you have the drivers for the controller installed... you have a profile loaded there is a default profile tucked away in your windows\system32 folder that gets loaded any time there is not a "user profile" in place. The file name changes slightly depending on which controller you are using and what version you drivers are but don't worry it's easy to find. Just open up your windows\system32 folder (for most of us that's c:\windows\system32\) and scroll sown to the files (not folders but files) beginning with the letter s you are looking for the one whose name starts with Sai and ends with .pr0 most of them will be SaiD0BAC.pr0 but your might be a little different it's the only .pr0 file in the systen 32 folder by the way. \ Now if you are like me you will want to rename that file rather than deleting it (just in case you ever want to put it back) just make sure that if you rename it... fyou can find it again if you need it. Once you rename the file you need to restart your computer. Restart your computer... RESTART YOUR COMPUTER. Ok perhaps that was a little excessive you only need to restart once, but if you don't restart the mode switch still won't show up. So... AFTER YOU HAVE REBOOTED Open LINDA and play with your mode switch a bit while watching your joysticks. you will notice that now the mode switch shows up as buttons... in the case of my pro flight yoke they are: mode 1 = 9 mode 2 = 10 mode 3 = 11 Now you can start to explore using the Shifted functiality in LINDA programming but you have to remember one extremely important thing. In this case I'm going to use mode 1 as my normal mode and mode 2 as my "Shifted" mode so just for argument sake I'll assign my headding bug to the C1:C2 switch on my yoke, C1 = button 7 which I set to Headding Bug Dec, and C2 = button 8 which I set to Headding bug Inc. Don't forget to add the commands to the both the "On Press" as well as the "On Repeat" sections so that you can hold c1 or c2 and have the Headding bug continue to increase ofr decrease while you hold. Next move your Mode selector to mode 2. If the mode selector was already on 2 move it off and then back to 2 so that you can tell which button it represents in LINDA. As I said earlier My mode 2 is button 10 so I will set 10 to GLOBAL SHIFT. Now hit save within LIDNA to save to buttons and then check the "Shifted" checbox rught under the save button. Don't PANIC all your buttons didn't just disappear. The screen switched to showing you the list of commands programmed in for ONLY while the "Shift" button is pressed. In this case button 10 or "Mode 2". Now you can set up the C1:C2 to something else like Rudder Trim for example. BUT there is one more important thing. As you may have already experienced you may have to reload the LUA engine (settings page right hand side) for the changes to be fully implimented. Now I said I would take you 1/2 way there and I just did. So as for the developers part??? How about the tittle of this post? Could you add multiple shift states to LINDA please? Pretty pretty please? Two shift states would be enought to use the pro flight gear with it's three modes but there may be need for more than that in some situations, depending on the controller. Now that I have the mode switch showing up I have every intention of using it. Absolutely no offense to Pete intended but I would much rather use a quick and simple ui such as LINDA to impliment it. The Consolidation that LINDA provides is outstanding!!

I'm still not sure weather or not the download is available so I'm posting a link here to another forum I recently joined where I have to scripts original scripts as well as the most recent versions posted. All future development on those scripts as well as others will be done on the other website since not only can I make scripts available for download right in the posts but it is a more likely place for lvl 2 and 3 immersion to be looking for them in the first place since it is they who need to tie those plane functions to knobs and switches in the first place. The link here is where I will be putting the scripts for the Duke specifically and I'm sure there will be others posting there as well so if you have need... feel free...Bao-http://forum.simflight.com/topic/69767-duke-turbine-scripts/

I didn't hear anything about mad dog pledging to publish any sort of event assignments, but as promised I uploaded the lua scripts that I wrote last night after giving them a quick shakedown the file is DukeLUAs.zip... I don't know how the system works here because I have not used this particular forum before, so I don't know when they will become available for download. I didn'st write one for the Cabin Pressure yet but I'll get to it as soon as my brain rests up a bit.Please let me know what bugs you find so I can take care of them as quickly as I can. So far they all work for me.Bao

I think you may misunderstand what I mean by lvl's 1, 2, and 3. It's about the immersion level and has nothing to do with how long someone has been flying sims or the level at which they participate in real world aviation. It's all about "the mouse in the cockpit" as we call it. Not necessarily the actual mouse mind you, but for example.Your basic level one simmer installs the software out of the box and most likely installs a joystick or flight stick of some kind and just flies... he may fly 90 hours a week for 10 years. But he is still a lvl 1 simmer. The level one refers rather to the hardware setup.. He only uses one keyboard for example.The level two simmer is a bit more advanced in the other hand... He or she feels the need to use more than one keyboard in order to reduce keyboard combinations to a single key-press and have keys or "buttons" on both sides of the controls to help simulate the reality if reaching with the left hand to flip switches that are on the pilots left side in the aircraft and keys on the right (ir even over head off to the right) to simulate switch panels in those locations. This simmer can generally has the desire for an exceptional 3d cockpit (like the one in the Duke) to help his "reality" stay tied to visually accuracy. This simmer also likes to employ the use of additional monitors for third party apps like flight planning software, weather tracking, and such.In my case I also like to keep my GNS's up on a separate monitor (down and to the right) so that I don't have to loose the ability to see my other gaugesor the horizon line but rather can just turn my head slightly and still have a peripheral view of the world and the rest of the plane. And since I have all the RXPGNS units listen for keystrokes independently from FSX and can be set up with their own keybindings I just have to move my hand over the controls for the GNS I have placed just below that monitor.Which brings me to level three.. This is what I'm transitioning to right now in my case for financial reasons it's a LONG transition. and relies (and will to continue to) heavily on inginuity spare parts broken stereos, VCR's, junk from the local dump, etc... But many of you have seen examples of the creature I am turning into... Were the "nut jobs" who build full scale cockpits in the spare room of our house or in a garage... in the case of one gentleman I read... In his warehouse downtown.Once this level is achieved the virtual cockpit is no longer needed. But during the transition... it is.I hope that helps to clear up the misunderstanding. Saying that I thought Ryan was a high lvl 1 or a lvl 2 was not in any way a putdown it was just a guestimation of the immersion level he flies at.. One KBD, IR Tracker, flight controlls (yolk or stick) single monitor (even if it's a movie screen) is a lvl 1 (ir and huge screen generally considered a HIGH lvl 1) Once you start buying or building extra key panels or using afternmarket (or home built) autopilot units, comstack and the like, you have crossed the threshold and are in danger... Your wife just may hold an intervention.Thankfully my wife understands completely (end even helps out. I hope one day to teach her to fly.As to the "Duke issues"I sniffed out most of the variables and knocked off a few LUA scripts to be run through last night in the wee hours of the morning giving me full hardware assignability to all the knobs and switches that can't be used with a basic event binding and now have FULL control over the plane from hardware through FSUIPC. Like I said it was in the wee hours of the morning as soon I polish them up a bit I'll make them available to anyone who wants to use themAnd Rob,Can we assume that so much of the Duke is simulated outside of FSX in preparation for implementation on other sim platforms with minimal updating? If so I will do my best to include functionality for all the switches that don't do anything in FSX but are still "switchable" in the Duke in case they are tied to simulator function later. Of corse this would be a lot easier and go a lot faster if I has an actual list of the variables rather than sifting through the aftermath to get them. Not to mention coders and scriptwriters far better than I could take a wack at it too and maybe together we could slay this beastMy goal in the end assuming I have time and brain function enough to pull it off is to write a "translator" script that listens for SC Events and then mimics the Duke equivalent setting for the entire plane, implementing change in the Duke only after it is confirmed to be in the wrong state of course. I wrote software for years and I absolutely understand if you can't provide a list to work from. But it may be worth talking with you business partners about. Listing the Variables in the PDF manual for reference might not be a bad Idea.At any rate I'll keep sifting in the meantime.Bao

Real world pilot... Really.. You of all people should appreciate the the desire and need for keeping a plane up to date with the latest equipment. Don't think that's realistic?? Than I challenge you to look at used ga planes for sale... Dukes even.http://www.controller.com/list/list.aspx?manu=BEECHCRAFT&mdltxt=B60+DUKEYou won't likely find any 2 that are identical. You know why. Because owners customize them to suit their needs. Many of those customizations happen right from the start with the ordering of the aircraft from the manufacturer. While others are completed later to improve on preexisting systems such as Swapping out the old radios for a pair of GNS 430 AW units or a pair of 530's for that matter, not to mention the extremely popular Storm 500 WX or the afore mentioned sandal HSI (available as OEM on the duke turbine I believe. If someone does write that gauge I can't put it in the plane because of narrow minded short sighted design flaws.And I don't care what anyone says. Having to use a mouse rather than flip an actual switch is not more realistic. As for the head gear... Go for it... Where I'm headed it's obsolete. I will simply turn my head and look at what is ACTUALLY beside me on the floor and wont have to pick up a mouse to use it.All I've been saying all along is that there are more than one level of user out there... Ryan... You seem to be an advanced level one or maybe a two. I don't know you well enough to know. My opinion is that unless a payware product this good takes all levels of use into consideration INCLUDING the people like me who are putting together actual full cockpits in front of concave projection screens and all the steps between a basic lvl 1 and the full sim like I'm building, it falls short of it's user as well as dollar earning potential especially when making it "comply" with the needs those different levels of user actually costs you less money because you spend less time and effort trying to prevent the customization of the plane and use pre existing commands and scripting rather than developing from scratch resulting in knobs and switches that wont respond to in came commands and therefore can't even be mapped to a simple keyboard shortcut by a lvl 1 or 2 user.Don't forget... Like I've said before. I'm not saying it's a bad plane... Quite the opposite it's a great plane in my opinion the best plane I own. I't almost the only thing I fly. (just ask my flying club) I just think that there are a few MAJOR problems with it that need to be addressed, and I think that payware plane designers in general need to think about a bigger picture when deciding weather or not to include a variation that a level 2 can customize with aftermarket gauges and equipment.And for goodness sake... make sure you knobs buttons and levers can be activated by mouse, keyboard shortcut, or direct input (simconnect in the case of FSX) so that it's usable by all levels of user, not just the guy who thinks there should be a mouse in every cockpit.Bao

No and NoRealAir is one of the companies out there that doesn't understand there are those of us who think using a mouse detracts from the"Reality" of the experience, as such most of the things in the cockpit can not be used by switch or keypress but MUST be handled with mouseclicks.They also don't realize that having d2 panels on screens below th3 main flight screen to simulate guages in an actual panel is more realistic than a 3d cockpit so they refuse to put out 3d 2d panels... Just like they refuse to put out a model that you can swap out guages and radios on EVERYTHING is permanently built into the aircraft model so that any customization "by the customer" is impossible. You can choose from a pre defined list of "alternate" avionics configurations but nothing more.The basics are all good though... Yolk, pedals, trims, hat.All that being said... I still love the plane. I just wish I could "make it my own" so to speak by doing things like swapping the transponder for example (among other things)Bao

Thanks a great deal for the lua script covering the oil doors. Not to sound greedy but has anyone found a way to do the same thing for any of the rest of them?Fuel Valvesinverter switchignition switches (not starter)all the power switches on the commstackcabin pressurecabin pressure climb ratecabin pressure dump switchAgain, not to sound greedy I just can't tell you how excited I was about the oil doors script, I would LOVE to be able to get the mouse out of my cockpit all together.Bao