C6_Hellfrog

to add in the asked list : could be best if it was multiwindowed : we could position each gauge at the place we want without having the non transparent background... main problem for pitbuilders...

ok but do you have BSVP working nice with this utility ?

I think without too many FPS drop ?

create a log file in the export.lua write values in it run BS after that read log file

nice good F16 pits have average cost > 2000 € without time spent and tools cost...and with many months of work... you can always have something interesting for much less... or you can also find passionated people spending much more... it is all about you but consider these costs : electronics spare parts (cable, switch, cards) wood, paint other peripherals (sticks, mods, screens, uupgrade of PC, and so on...) tools you will need but don't have depending on your skills and the size of your project... it may quickly grow... and another cost, not so financiary : time spent without your wife and children if you have any the place where it will seat in your house the dust and all that sort of trouble (noise, disorder...) maybe some troubles may happen here... a point to consider Before !

Hi, many factors inside : desynchronization is usual if you run SIOC and BS on the same rig, and it depends on the CPU load (high level mission...) and CPU frequency (i7, OVC...) and the size of lua subrutines to run, and their place (each frame, each 1/t seconds) and the complexity of SIOC program... if you run very complex cockpit programmation, best is to use another PC for SIOC, if you can... or to upgrade yours (although it is a good specs indeed, but 3.5 GHz only, and not best use of multicores on BS...) and Seven is best than XP for BS...

glad to hear such good news and such help between pitbuilders ! congrats for that nice job guys !

hi yes it is exactly like you said : see Kpaw profile !

one french user reported last year he bought it : precision durability feeling were satisfying... furthermore it was a private pilot on retirement

happy to see that it rocks ! contrario could not be possible after all that work ! you'll gain many gratitude and reputation... but... with all that stuff, you do will have to train your pilots skills, otherwise you will have some bad comments from your fly partners... such excellence in cockpit can't acommodate with poor piloting skills...

search thread BSVP for gauges

the crazyness of this man may be helpfull ! These last days I was making some cleaning and organization in my garage , and I dropped many things to garbage... My wife asked me why I didn't throw all these parts of foam... Now I know what to answer ! :lol: :thumbup: One good thing is that she doesn't read this forum ! :D

hum... what about the value to put in pValue ? where find it ? could upgrade my exelsheat but don't know or don't find any pValue ... ???

in the script for touchpal, in export.lua, you have in case you send 'S' (Setcommand) and not C (performclickableaction), in the input function, two parameters for setcommand... so it should be as said by TheBest. have not tested personnaly because my office is out of order for some handwork to upgrade it ... so I have only one screen in order and don't want to rewrite all stuff for just some days... will test later... in some days.

Still one problem / 1st question on this topic : didn't found anyway to for the following KEYS from keyboard : (non exhaustive) Parking Brake : LSht z ? Shkval : i or o ? RPM : Pgup Dn + RAlt RSht ? only soluce : map on HOTAS ?

I think you need to have a tranparent part of your background on the touchpal profile, and you have to place the BSVP or LOVP just at that place, under/behind the touchpal window to have it work. you may have two computers but it is not necessary

yes it does from ext view (autopilot, door and so on are ok) EDIT : if you downoaded 1st version of xls sheet, please update to last one, much more complete, see some posts previous

the only lack from HID macro are : lack of support for 64 bits, and no recognize or differenciation between left and right CTL ALT SHF. you may also try to use Glovepie fopr more advanced programming with different interfaces, a new version is in development, and an update for 64 bits compatibility for PPJoy.exe is also on study. But not totally finished at the time. But older versions are cool if you are under 32 bits OS.

Do I have all understood ? you push the button, it closes the electrical circuit, then the motor is on and it turns to move the "rope", then when the move is enough to activate the brake lever, a piece of something glued on the rope push another contactor to ? ? ? (re open the circuit and stop the motor ?) , (but how does it stay on tension ?) then you unpush your button and the motor is free and the rope goes back due to the effect of springs. nice done. may you confirm or detail in place of my ??? please.

file to use DeviceName, DeviceID, KeyName, KeyID with getDevice():SetCommand() update : much more completed ! final version of the datasheet : DeviceName, DeviceID, KeyName, KeyID only a few keys from commands_defs.lua have no replication in other *.lua. _Datas GetDevice_SetCommand.zip

and you did it very well ! many other people had the same problem as memento10 ! One question more : for many actions you may use the classic 'performclickableAction' way or this new 'getdevice:setcommand' way... is there a difference between the two ones ? I think about FPS hit on large export.lua files or on complex stuff (SIOC multiscreen BSVP BS network) ?

a file for work in progress to save time commands_defs : this file contains many keys, but not sorted by device order, so I managed to process lua files to sort a bit all that stuff and compile it in an exel sheet. compiling files *.lua in .\scripts\aircrafts\ka50\cockpit and commands_def.lua and devices.lua : exel sheet with device_name, deviceID, key_name, key_ID, sorted by devices : see linked file xls 2010 format lines from commands_defs.lua not in this sheet are keynames not investigated at this time : need to process lua files in sub folders from .\scripts\aircrafts\ka50\cockpit... will update when achieved... it is work in progress if anyone has corrections to add or remarks... appreciated... since all interested peolple by this thread will have to search these informations, if it may save some time, it is usefull... EDIT : file removed : see post 21 for an update

working on it... will test with touchpal (stil don't have SIOC, but same way of working) from this WE, and post results ASAP...

nice shot ! will study that ASAP ! [EDIT] files are in .\scripts\aircrafts\ka50 and .\scripts\aircrafts\ka50\cockpit once you have looked it and read it, it seems to be so easy... but it wasn't... as no one said it before !

hey, have a look at this thread http://forums.eagle.ru/showthread.php?t=56067 ! posts 8 -10