WB_FlashOver

LOL Scot, I know what you speak of. Real World really gets in the way of playing...(programming). In your time Sir. No worries.

Hello Scot, Just curious about this slow repeat issue. I'm sure you're busy so I'm just checking in. Have a great day. FlashO

I suppose it's not needed to mention this as it is a OnRepeat issue but it is not just the trim. My cabin vent control and radio volume controls in the A2A B17 are just as jumpy and slow. FlashO

Hello Scot, Thanks for the reply Sir. Tonight it is back to very very jumpy and slow. I have trim set on the index finger hat switch on my throttle hand on the X52 pro. I have up/dn fast un-shifted and up/dn regular shifted. I've tried reloading Lua engine, no joy. I've tried selecting Joystick page, no joy. I've tried multiple syncing, no joy. I have tried restarting LINDA, no joy. For now I have trim set in FSUIPC. I'm sure you will have it ready for the next release. This truly is a great program and I'm very appreciative for it. Hats off to you. FlashO

Thank you Gregg, I had made a habit of syncing twice and clicking the joystick page on versions prior to 2.6.8 but on 2.6.8 it was working without doing this. So maybe for the time being I need to go back to my normal startup steps. Thanks again for the reply. FlashO

Well, belay my last. I reinstalled 2.6.7 and 2.6.8 and then 2.7.0 again and for some reason it is better. The A2A P51 is still jumpy but it always has been. Last night the A2A B17 was terrible but after reinstalling it is smooth again. I followed instructions of removing linda & linda-cfg folders as well as ipcReady.lua, LINDA.exe and linda.lua and then placing the new files/folders into the modules folder. Thanks again FlashO

Hello developers, First let me say thanks again for the great program. Each revision gets better. I am having issues with 2.7.0 with On Repeat commands though. 2.6.8 would give very smooth and steady trim adjustments where 2.7.0 is jumpy with about 1/2 second pauses between wheel movements. This is happening on a friends PC as well but he's on Win 7 Pro 64. FSX & FSX-SE, Win 10 Pro 64, Saitek X52 Pro, FSUIPC4 v4.949. Looking forward to more flying with LINDA. FlashO

Hello again guenseli, Problem solved. It seems to be an issue with the aircraft folder name. I've changed the military version folder name under simobjects\airplanes\ from WoP3_P51D to WoP3_P51D_Mil, then edited the file ident.Lua to point to new ac folder name. I'm now able to create separate controls for each version. I've only done this a few hours ago so we'll see if it holds over time. I've tested it several times, so far so good. This will create issues for any updates from A2A but that is easy to work around. FlashO

Hello again, It's been a while sense we discussed this topic. I've tried the steps above but had no joy with it. I was hoping to revive this topic one last time to see if anyone has had any luck with this. Thanks again FlashO

Hello OldFlyboy, I don't have that plane but I know just what you are trying to do. I've done the same thing on my A2A B-17. These commands may not work for your plane but you can get an idea of what I have going on in this sequence. I did not include engines 1 & 2 to save space. I would recommend not using key strokes but edit the .lua to sequence tasks as you wish. In the B-17 the start sequence is 3-4-1-2. So, after toggling all batteries and inverter I go to the button (Shift+Wheel 39 Up) (Saitek X52 Pro) which is "function B17_Starting_3 ()" and this handles all tasks specific for starting engine three except for the primer and starter. I've put random sleeps between each command from 150ms to 250ms for added visual appeal. You will need to read the manual to know how to use the proper commands for your aircraft. function B17_Starting_3 () ipc.writeLvar("L:MasterIgnitionSwitch", 1) _sleep(150, 250) ipc.writeLvar("L:EngineSelection", 4) _sleep(150, 250) ipc.writeSB("09C2", 3) --mag3 _sleep(150, 250) ipc.writeLvar("L:FireEngineSelected", 3) _sleep(150, 250) ipc.writeLvar("L:MixtureRatioLever3Position", 2) _sleep(150, 250) B17_FuelValve3_on () _sleep(150, 250) ipc.setbitsUW("3a18", 1) --fuel pump end The next button (Shift+34) primes engine 3 and then next button (Shift+33) on press turns over starter and on release meshes starter. And then when I select engine 4 it also turns on engine three generator. function B17_Starting_4 () ipc.writeLvar("L:Eng3_GeneratorSwitch", 1) _sleep(150, 250) ipc.writeLvar("L:EngineSelection", 8) ipc.writeSB("0A5A", 3) --mag4 _sleep(150, 250) ipc.writeLvar("L:FireEngineSelected", 4) _sleep(150, 250) ipc.writeLvar("L:MixtureRatioLever4Position", 2) _sleep(150, 250) B17_FuelValve4_on () _sleep(150, 250) ipc.setbitsUW("3958", 1) --fuel pump end The things you can do with LINDA are astounding. It takes some time to get the hang of it but it's well worth the time and effort. I hope this helps you some. Cheers FlashO

Yeah, I knew enough to add the files to the linda-cfg side of the folder structure. Here are my civ and mil file/folder stucture. https://dl.dropboxusercontent.com/u/33534044/modules.rar I believe it is all correct and yet does not work. Still pulls from the mil version for both even though LINDA syncs the civ automatically and the correct controls load into the Joysticks window. FlashO

Hello guenseli, Ok, I've followed your suggestions. They are a little different sequence than what I did originally but the outcome is the same. Only difference is that I copied the files in ~\Modules\linda-cfg\aircrafts\WoP3 P51D Civ to the new folder ~\Modules\linda-cfg\aircrafts\WoP3 P51D Mil. Half my work is done already this way. - All 'civ' controls work. - Create new module per instructions. - Edit new 'mil' controls - Everything is OkeyDokey - Change aircraft to 'civ' and it only uses controls from 'mil'. - Linda - Joysticks is showing proper controls for synced 'civ' aircraft but controls being sent to game are 'mil' controls. - Use Linda gui to delete 'mil' module and immediately the 'civ' starts to work properly. - ident.lua for each is calling to the correct folder name in ~\SimObjects\Airplanes, i.e. WoP3_P51D for 'mil' and WoP3_P51D_Civ for 'civ'. Maybe it is not possible to do this. Maybe it is an A2A coding issue. Oh well, it would've be nice. If you have another idea I'd be glad to try it. Thanks again! FlashO

Hi guenseli, Actually there is nothing wrong with the module. I would really like to have two separate modules, one for mil and one for civ. The civilian has a lot of auto pilot things I like to set but then when I fly the military I have dead buttons that cannot be programmed separately from the civilian. Is there already separate modules? If so where do I find them? Can I copy the civilian to a new module with a special name for the military? Thanks again for the program and for the reply! FlashO

Hello, Let me say first that LINDA is one of the best things to come to FSX in a long time. Thanks so much for the great program. I am attempting to create separate modules for the Mil & Civ versions of the A2A P-51. It seems that things get really confused and start pulling from default FSX for some controls and from the civilian for other controls and from the military for other controls. I have made all the adjustments for my civilian P-51 and the module is calling to the WoP3_P51D folder but should be calling to the WoP3_P51D_civ folder. Then I used the 'copy from existing' and copied the civilian to a new module named WoP3_P51_mil. I made sure that the aircraft search string pointed to the WoP3_P51D (which is the military version) folder and started tweaking settings to fit the military version. No joy with it. I made sure the ident.lua had the proper aircraft folder addressed as well for both versions. I'm sure I'm missing a simple step or two to make this work. LINDA calles to a specific aircraft folder so I am not sure why the civilian is calling to the military folder. I am sorry if there is already a topic on this but I was unable to locate it if so. Much obliged for any help. FlashO