DaveSimBuildGuy
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by DaveSimBuildGuy
-
-
Thanks, Spokes. I'll look into what you've mentioned and see what I can come up with. Happy to buy you one if you reckon you can sort something out for me ;)
Cheers, Dave...
-
No worries with the default aircraft. Verified.
Cheers
Dave
-
Thanks for getting back to me, Pete. I should've been more clear. I programmed the release into it simply as an experiment. I tried about every combination I could come up with using every command with "ADF" in it, particularly those with "RADIO ADF IDENT" in them. My suspicion is that the software designer used some kind of roundabout method to make the audio panel and other functions work. FSUIPC does seem to have some limited influence of the functions, but I can't seem to get beyond what I described in my original post.
Cheers, Dave.
-
G'day Pete and/or Pro Simmers,
I'm having a bit of a problem with the audio panel in the NemethDesigns payware BK-117 flight model. It seems they've gone out if their way to make it, basically, not compatible with anything conventional. I need the flight model for a hardware simulator, half-complete for a rescue organisation. I'm using a mix of Elite hardware and Leo Bodnar USB boards.
For the life of me, I cannot figure out how to interface with the audio panel (let's say ADF IDENT, for now) in a meaningful way. Using FSUIPC to configure buttons, the best I coulD achieve this far is to get the graphical button to flicker on, then immediately off. When the log is running, the inputs indicated are RADIO ADF IDENT ENABLE and DISABLE. I Tried that, and it worked initially but not staying on. I changed it up by adding the "when released) portion to disable. Now, the button stays engaged as long as the physical button is being held, but nothing to keep it held.
I restarted, and lost even that functionality. Now, the button needed to be configured for the FS command, "RADIO ADF IDENT TOGGLE," but still, it's not persistant and will only flicker on, then off. Now, I'm unable to keep it on by keeping the physical button pushed.
I attempted a mouse macro as well, but alas, nothing is picked up by FSUIPC.
Is there any hope here? I'm not in the slightest a programming type, but I'll learn as I need to.
Cheers, Dave
-
All aircraft, across two PC's.
No, Pete, I'm not turning them too fast. I thought I was quite clear about that. Oh, and yes, the "fix control acceleration" option was selected. I found an alternate fix and am good to go. Thanks for your time.
-
G'day Pete,
Still no luck. I brought a generic, known good encoder out to troubleshoot and have the same problems. Set to VOR1 Obi Inc/Dec. I've also set the heading bug up the same way, and it is behaving the same way. Not jumping an increment, but up to 10° at a time, randomly. This has nothing to do with the speed at which the encoder is being twisted. I'm doing so very slowly. I am experiencing the same problem when manipulation the course or heading bug with a keyboard shortcut.
Strangely, those rogue encoders are working just fine for heading bug and Kohlsman, though FSUIPC see that as Heading Bug Set and Kohlsman set, yet it works the way it should. Here is a portion of the log showing those encoders. I guess I'm hoping you might recognize the behaviour so I can hunt down whatever is controlling their function. Again... Not FSX, not FSUIPC, and not seen in windows USB Game controllers.
832796 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 339 (0x00000153) VOR1_SET833155 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 338 (0x00000152) VOR1_SET833295 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 337 (0x00000151) VOR1_SET834559 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 336 (0x00000150) VOR1_SET834996 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 335 (0x0000014f) VOR1_SET835635 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 334 (0x0000014e) VOR1_SET838584 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 333 (0x0000014d) VOR1_SET839052 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 332 (0x0000014c) VOR1_SET844387 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16207 (0x00003f4f) KOHLSMAN_SET844481 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16204 (0x00003f4c) KOHLSMAN_SET844590 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16201 (0x00003f49) KOHLSMAN_SET844621 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16198 (0x00003f46) KOHLSMAN_SET844715 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16195 (0x00003f43) KOHLSMAN_SET845417 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16198 (0x00003f46) KOHLSMAN_SET845495 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16201 (0x00003f49) KOHLSMAN_SET845588 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16204 (0x00003f4c) KOHLSMAN_SET845760 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16207 (0x00003f4f) KOHLSMAN_SET848505 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 94 (0x0000005e) HEADING_BUG_SET848599 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 93 (0x0000005d) HEADING_BUG_SET848677 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 92 (0x0000005c) HEADING_BUG_SET849613 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 93 (0x0000005d) HEADING_BUG_SET849675 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 94 (0x0000005e) HEADING_BUG_SET849785 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 95 (0x0000005f) HEADING_BUG_SET849816 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 96 (0x00000060) HEADING_BUG_SET849909 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 97 (0x00000061) HEADING_BUG_SETAnd the following will be for first heading bug and vor1 obi on the known, good encoders:77984 [buttons] now profile-specific:77984 47=P0,21,K67,1077984 102=P2,15,K66,1088093 Button changed: bRef=0, Joy=5, Btn=1, Pressed88093 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,088093 FS Control Sent: Ctrl=65880, Param=088156 Button changed: bRef=0, Joy=5, Btn=1, Released88359 Button changed: bRef=0, Joy=5, Btn=1, Pressed88359 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,088359 FS Control Sent: Ctrl=65880, Param=088390 Button changed: bRef=0, Joy=5, Btn=1, Released89731 Button changed: bRef=0, Joy=5, Btn=1, Pressed89731 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,089731 FS Control Sent: Ctrl=65880, Param=089794 Button changed: bRef=0, Joy=5, Btn=1, Released90137 Button changed: bRef=0, Joy=5, Btn=1, Pressed90137 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,090137 FS Control Sent: Ctrl=65880, Param=090168 Button changed: bRef=0, Joy=5, Btn=1, Released91245 Button changed: bRef=0, Joy=5, Btn=1, Pressed91245 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,091245 FS Control Sent: Ctrl=65880, Param=091307 Button changed: bRef=0, Joy=5, Btn=1, Released92103 Button changed: bRef=0, Joy=5, Btn=1, Pressed92103 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 103=P5,1,C65880,092103 FS Control Sent: Ctrl=65880, Param=092149 Button changed: bRef=0, Joy=5, Btn=1, Released94723 Button changed: bRef=0, Joy=5, Btn=2, Pressed94723 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,094723 FS Control Sent: Ctrl=65663, Param=094786 Button changed: bRef=0, Joy=5, Btn=2, Released94895 Button changed: bRef=0, Joy=5, Btn=2, Pressed94895 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,094895 FS Control Sent: Ctrl=65663, Param=094926 Button changed: bRef=0, Joy=5, Btn=2, Released95862 Button changed: bRef=0, Joy=5, Btn=2, Pressed95862 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,095862 FS Control Sent: Ctrl=65663, Param=095893 Button changed: bRef=0, Joy=5, Btn=2, Released96003 Button changed: bRef=0, Joy=5, Btn=2, Pressed96003 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,096003 FS Control Sent: Ctrl=65663, Param=096034 Button changed: bRef=0, Joy=5, Btn=2, Released96970 Button changed: bRef=0, Joy=5, Btn=2, Pressed96970 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,096970 FS Control Sent: Ctrl=65663, Param=097017 Button changed: bRef=0, Joy=5, Btn=2, Released97079 Button changed: bRef=0, Joy=5, Btn=2, Pressed97079 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,097079 FS Control Sent: Ctrl=65663, Param=097110 Button changed: bRef=0, Joy=5, Btn=2, Released98452 Button changed: bRef=0, Joy=5, Btn=2, Pressed98452 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,098452 FS Control Sent: Ctrl=65663, Param=098483 Button changed: bRef=0, Joy=5, Btn=2, Released98561 Button changed: bRef=0, Joy=5, Btn=2, Pressed98561 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,098561 FS Control Sent: Ctrl=65663, Param=098623 Button changed: bRef=0, Joy=5, Btn=2, Released99996 Button changed: bRef=0, Joy=5, Btn=2, Pressed99996 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,099996 FS Control Sent: Ctrl=65663, Param=0100027 Button changed: bRef=0, Joy=5, Btn=2, Released100105 Button changed: bRef=0, Joy=5, Btn=2, Pressed100105 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0100105 FS Control Sent: Ctrl=65663, Param=0100137 Button changed: bRef=0, Joy=5, Btn=2, Released101572 Button changed: bRef=0, Joy=5, Btn=2, Pressed101572 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0101572 FS Control Sent: Ctrl=65663, Param=0101650 Button changed: bRef=0, Joy=5, Btn=2, Released101775 Button changed: bRef=0, Joy=5, Btn=2, Pressed101775 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0101775 FS Control Sent: Ctrl=65663, Param=0101806 Button changed: bRef=0, Joy=5, Btn=2, Released104224 Button changed: bRef=0, Joy=5, Btn=2, Pressed104224 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0104224 FS Control Sent: Ctrl=65663, Param=0104255 Button changed: bRef=0, Joy=5, Btn=2, Released104364 Button changed: bRef=0, Joy=5, Btn=2, Pressed104364 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0104364 FS Control Sent: Ctrl=65663, Param=0104395 Button changed: bRef=0, Joy=5, Btn=2, Released107110 Button changed: bRef=0, Joy=5, Btn=2, Pressed107110 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0107110 FS Control Sent: Ctrl=65663, Param=0107141 Button changed: bRef=0, Joy=5, Btn=2, Released107313 Button changed: bRef=0, Joy=5, Btn=2, Pressed107313 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0107313 FS Control Sent: Ctrl=65663, Param=0107375 Button changed: bRef=0, Joy=5, Btn=2, Released110635 Button changed: bRef=0, Joy=5, Btn=2, Pressed110635 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0110635 FS Control Sent: Ctrl=65663, Param=0110698 Button changed: bRef=0, Joy=5, Btn=2, Released110838 Button changed: bRef=0, Joy=5, Btn=2, Pressed110838 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0110838 FS Control Sent: Ctrl=65663, Param=0110869 Button changed: bRef=0, Joy=5, Btn=2, Released112008 Button changed: bRef=0, Joy=5, Btn=2, Pressed112008 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0112008 FS Control Sent: Ctrl=65663, Param=0112071 Button changed: bRef=0, Joy=5, Btn=2, Released112804 Button changed: bRef=0, Joy=5, Btn=2, Pressed112804 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0112819 FS Control Sent: Ctrl=65663, Param=0112851 Button changed: bRef=0, Joy=5, Btn=2, Released113911 Button changed: bRef=0, Joy=5, Btn=2, Pressed113927 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0113927 FS Control Sent: Ctrl=65663, Param=0113989 Button changed: bRef=0, Joy=5, Btn=2, Released114021 Button changed: bRef=0, Joy=5, Btn=2, Pressed114021 [buttons.Eurocopter BK-117 Final Edition ADAC Auxtank] 106=P5,2,C65663,0114021 FS Control Sent: Ctrl=65663, Param=0114083 Button changed: bRef=0, Joy=5, Btn=2, Released128014 Sim stopped: average frame rate for last 50 secs = 29.8 fps135908 System time = 09/12/2014 23:49:43, Simulator time = 12:06:44 (02:06Z)135908 *** FSUIPC log file being closedI've got a video coming if I can ever get the bloody thing upload to YouTubeCheersDave -
The only thing I could think of would be the Elite drivers package for the avionics. It doesn't allow for much customisation, and I'm thinking it might some how have gotten hold of the two based on how they were wired to their respective boards. The unit has too many boards. I'll start troubleshooting. Thanks for the input.
Cheers
Dave.
-
Thanks Pete,
I'll check hothouse two conditions you mentioned. Certainly, I'm turning them slowly, one click at a time. The things just weren't built for anything more.
As to the 3 rogue encoders, they were never given an assignment by a human being. The machine is freshly set up, new software, all new installations and nothing carried over. I was concerned the encoders were no good, as I could register a pulse with any of the others in the Windows USB game controllers configuration. Similarly, I checked FSUIPC to assign, and same. They didn't registers.
That's when it got interesting. I was playing around with all the encoders and quite accidentally, twisted the nob the should be the Pilot side Heading Bug. And there it went, just as it was supposed to. I went back to Windows and FSUIPC and same result, nothing.
Next, I started up the log and started watching the text roll. When I twisted the heading but encoder, sure enough, FSUIPC saw and reported it correctly as Heading Bug Inc/Dec. It reported the other errant encoders as "vor1 set," which will,one day be assigned course bug, and the other, for Baro, as "Kohlsman." Back to buttons assignment I went, and nothing. Zip. Back to Windows and nothing.
I checked FSX controls for any assignments that may have magically appeared, nothing. Full-on flummoxed.
One thing I did notice... The Course (OBS) bug, when set to "Vor1 set" behaved as I would like "vor1 obi inc/dec" to behave, only it only goes in one direction, regardless of the direction of the twist. One degree increments. Is there any way to make that one goes both ways, or forget it and keep, working on "vor1 obi inc/dec?"
By the way, I very much appreciate your personal responses to these assistance requests. It is rare.
Cheers
Dave
-
Exact process for choosing the OBS decrement function of VOR1.
1. Bring up FSUIPC
2. Choose "Buttons + Switches tab
3. Check "Profile Specific"
4. Twist the encoder left
5. Check "Select for FS Control." and click drop down.
6. Select "Vor1 Obi Dec."
I also have an interesting situation occurring with 3 of my encoders. They're all connected to the same board as the other encoders, but FSUIPC cannot see them to assign a function, also, FSX won't see them. Strangely enough, the FSUIPC log DOES see them, and they have functions assigned that work in FSX. I haven't seen anything like this before. They also can't be seen in Windows USB game controller settings.
Cheers
Dave
-
Ok, no... That was short lived. Still the same problem :(
-
Ohhhhhhh, thank you, Google :) You too, Mr. Dowson. Found it under Miscellaneous "fix control acceleration."
Cheers
Dave
-
Hello,
I'm trying to assign the "OBS" function of a VOR display and am having some problems. What I am getting is incremental jumps, a degree at a time, and then monster leaps of many degrees at a time. I understand this to be a function of FSX, but is there a way to reign it in through FSUIPC? I'm not yet at the Lua programming or Offset use phase. At the moment, all I know how to do is assign FSX or FSUIPC commands from the drop downs.
I need this for a rotary encoder. I need it to increase or decrease only one degree at a time. As always, all help very much appreciated.
Cheers
Dave
-
Oh... And then I read that the event logging was in FSUIPC. Sweet, I'll,be in that tomorrow.
-
Pete,
Love the idea of event logging. I had no idea FSX had such a facility, or domyou mean within FSUIPC? Either way, I'll give that a go tomorrow. The model has a fairly decent startup procedure that they only describe using the 3D cockpit.
I'm looking forward to taking your software to the burning edges of awesome. It seems as though it's all there. Oh... I know nothing of code, and I know to achieve what I want I will need to. Any ideas for the best language to start with?
Thanks Again,
Dave
-
Pete and Ian,
Thanks for the responses. I need, quite simply, to learn more about FSUPIC and Lua configurations. Just a bit stuck for time on this. In the previous installation, they had the "Power Levellers," through axis confirmation set to run both "axis prop set," and "axis mixture set," so Pete, you may be on to something there. The problem is that the pilots said it was more of a toy thing and it didn't work properly, anyway.
I tried yesterday using them both as mixture and as the combination mentioned above. I used the joystick calibration menu to set 3 points for closed (I think, forgot the wording), idle, and fully open. They results were interesting, at best, and didn't allow for proper startup (or any startup).
I had a go at configuring a mouse macro, both in FSUIPC3 on FS9 and FSUIP4 on and FSX machine. I followed the pop-up instructions and also instructions from an AvSim post and I came up empty. When I got to the part where I chose to start a macro (information missing in the dialogue here), I ok'd out to the cockpit view and left-clicked for a selection. That's as far as it got with no further intervention from FSUIPC. I tried it several times, to no avail. I put it down to incompatibility between FSUIPC and the flight model.
I'll keep cracking away at it. I guess I was hoping someone had come across something like this.
Cheers
Dave
-
G'day, You lot! I'm not even a Padawan level FSUIPC user, folks, my apologies for that. I do intend to grow in the force in such a way that I can be of use to others. Currently, I am having a problem with a simulator I am finishing off for a rescue organisation. The unit is set to model a BK-117 B2 and I am using the freeware Icaro BK-117 Final edition.
The model came with no documentation for the separate systems on the aircraft, And I have NO idea how to get it's power control levers to act as they should in FSX/FSUIPC. I am not a script writer, or Lua programmer. The shameful truth is I have very little time to finish this and I need to b able to do it through the UI or with some snappy ini instruction from an FSUIPC pro. I can't find ANYTHING in the available FS controls that will allow for fuel flow. I need "cutoff," "idle," and "fly" for each of 2 engines. The controls are a twin axis fed to FSX through a Leo Bodnar board. That's the most of it, anything anyone could do to help me will be appreciated most heartily!
Please let me know what further information might be required.
Cheers
Dave
-
Hello, Pete, or anyone who knows anything about FSUIPC and is reading this:
I'm having a problems with a fairly complex BK-117 simulator using the "EuroCopter BK-117 Final Edition" freeware flight model. The setup was done in FS9 with FSUIPC3. The updated setup has been done on a new. PC with all of the same IO devices. I'm in a bit of a time crunch, so redoing all of the offsets(?) manually is out of the questions.
I did try copy the pertinent portions of the FSUIPC.in to the new FSUIPC4.ini, but no joy. I understand from what I read above that the different axis might be a problem due to the way windows log and categorises them,mans I acknowledge there is a fix for that, as mentioned. Here are a few questions:
1. Should the new implementation of FSUIPC see, and be able to import the "profile" from the old setup? This I have been unable to achieve.
2. Will Windows assignment of different USB devices also pertain to the programming of button functions? Replacing the button behaviour section of FSUIPC4.ini with a paste from the old ini brought me no joy.
3. Where, exactly, is the facility for change the assignments if axis etc., to a more universally recognised naming system for FSUIPC?
Thanks!
Dave.
Configuring the ND BK-117
in FSUIPC Support Pete Dowson Modules
Posted
G'day Roman,
flying today, I'll have a look at it tonight or tomorrow. I REALLY appreciate it!
Cheers, Dave...