rustam
-
Posts
39 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by rustam
-
-
Thank you VERY MUCH, Glenn!!!
I do appreciate your time and FANTASTIC skills! :)
Take care,
Rustam
-
Hi there,
As mentioned in the User Guide, some 3rd-party aircraft "use the more recent technique of having gauges in XML. Those are also not susceptible to "Mouse Macros". That's exactly the case with SibWings Antonov An-2 which initiates LVars through swan2.DLL. So, I guess I won't be able to use mouse macros for this aircraft, as also been proven by numerous tests from my side with the latest versions of the aircraft and FSUIPC (registered).
So, I've decided to use another approach by making a LUA plugin similar to A2A Spitfire but it contains more than one function tailored specifically for that particular aircraft model. I would be happy to limit myself to default FSX controls managed through FSUIPC.INI but the usage of a LUA plugin is necessary since some of the switches are bound to LVars only - like the inertial clutch and the oil shutter mechanism.
How can I assign buttons and keypresses on my Saitek X52 Pro to be able to call different functions from the same LUA file without using macros or LINDA? Is it ever possible through FSUIPC.INI?!
Thanks!
Rustam
-
Glenn,
Can you reupload this file please? Both links seem to be dead...
Thanks!
-
Hi there,
I've been using FSUIPC4 for years but I always had a difficulty in setting it right. I also use AS2012 as my external wx program. This time (after re-installing FSX) I decided NOT to touch any settings except those for controlling devices (Saitek X52 Pro in my case) since from what I can read in the FSUIPC manual, the weather and visibility options are optional unless controlled by external weather program. Well, you can send me back to ActiveSky forums to get the answer but logically thinking - do I really need to apply say wind or pressure smoothing settings through FSUIPC if they in fact need to be controlled by AS2012 (or any other external WX application). Or, am I missing smth here?!?
So, if this is the case can I leave FSUIPC4 default settings as-is and let AS2012 control all weather related operations? Any recommendation or advise is highly appreciated.
Thank you!
Rustam Alhas
-
Hi again,
I can now firmly confirm that Problem no.1 is SOLVED! :) Indeed, there was no "Logbook.bin" file inside "Flight Simulator X Files" but as soon as I created "text.bin" as per your recommendation, FSC stopped popping up that nasty message again... Thank you very much for your prompt support!!!
As to "Intersection vs. Navaids" problem, sorry but I still cannot grasp the idea behind "philosophy of the FSCommander". :???: And the reason is FSC doesn't stick to the same philosophy when it concerns "Navaid Plan" option but "changes its mind" when it comes to "High Alt Plan". This is confusing, don't you think?!? Why to compile one flightplan with navaids properly shown and the other one - NONE at all?!?
Once again, thanks a lot for your help!
-
Hi Volker,
Thank you for your reply! I thoroughly read it but, unfortunately, did get NONE of my questions answered. Here is why:
1. Reading the full thread you provided (plus additional links contained therein) shows that the problem still remains unsolved. Further, I have already read that thread, especially Ian's (baw19) and Kees's (khoubolt) replies and FSC manual Chapter 5.4 and the rest before posting here. You can see screens of my "Save/Load Flight Plan" window, if this helps.
2. Both flight-plans in your attachment are of no help either! Please read below:
(i) EDDK-EDDH-NAV.pln is the plan based on navaids route but I already stated above that:
;This problem does NOT happen though when I export FSX flightplan either with default FSX, FSC "Navaids Plan"...(ii) EDDK-EDDH-HI.pln is based on "High Alt Route" option - the option I am interested in - but instead of answering my question it replicates the same problem I have already. If you read my first post carefully, you can see that your flightplan also defines navaids as intersections. E.g., OSN is actually Osnabruck VOR (Germany) but your flightplan shows it as an intersection... Well, I'm ready to admit that any checkpoint on a particular route IS an intersection per se but I believe FSC must at least define it correctly in the flightplan, as is the case with "Navaids Plan" option. ;)
This is also true when the flightplan is visualized in FSC. E.g., as you can see from the image below, I used "High Alt Plan" option to compile a flightplan from KLAX to KJFK which shows a total of 4 (four) navaids (together with frequencies) along the hi-alt route:
# SLI, Seal Beach
# TRM, Thermal
# PKE, Parker
# DRK, Drake
But all of them are indicated as intersections both in the FSX flightplan (.pln) and in FSC (green triangles)... That's the problem!!!
Hope this clarifies the situation and helps you better visualize the problems!
PS: Ah, in order not to bother you with further questions, I have (i) FSC installed with Admin rights under root C:\; (ii) FSX is on the root of drive D:\ and installed "For All Users"; (iii) My system is Windows 7.
Thank you!
Rustam
-
Hi there,
This was asked several times before and I read recent and old posts about the "FSX folder paths" problem but as far as I understood it still remains valid with v9.1.1. I keep getting the error message when I go to the paths section of the save dialogue box "FSX flight plan folder unspecified" even though it is specified both in paths selection window and FSC.ini.
The other problem occurs when I try to save/export a flightplan in FSX format (.PLN file) - when I open it after saving all XML values under <ATCWaypointType> show "Intersection" although some of the check points along the route are VORs and NDBs and the correct way would be <ATCWaypointType>VOR</ATCWaypointType> for VOR and <ATCWaypointType>NDB</ATCWaypointType> for NDB. I can only guess whether it's a navaid or not only by its 3-letter identifier. Here is the order of export I usually use:
1- Click on "Show Flight Plan"
2- Insert departure and destination airports into the opened textbox "INSERT DEPARTURE AND DESTINATION ICAO CODE..." and press Enter
3- Press "High Alt Plan"
4- FSC calculates and retrieves the route points, distances, bearings, and even the frequencies of navaids but... STILL shows (and defines in .PLN file) navaids as intersections... :( This problem does NOT happen though when I export FSX flightplan either with default FSX, FSC "Navaids Plan" or e.g., Plan-G.
Can anyone explain me WHY FSC exports PLN files this way?!?
Thank you!
-
Hi Pete,
Here is the answer from Doug Kallen (a.k.a PropTrash @ FSDeveloper.com) who is the author of aircraft in question:
In order to separate the light switches from the circuit breakers I made use of local variables to animate each part. In the Stearman, the animation is driven by the local variable, and a key event is sent to the appropriate light circuit at the same time. This allows the circuit breaker and switch to operate independently of each other and still open/close the light circuit.With that in mind, I doubt FSUIPC will be able to work as you want it too, unless it supports local variables as well as key events. It’s been years since I’ve used FSUIPC, so I have no idea if it can do that. You might ask Pete Dowson at his support forum if it does have that capability, and if so, I can supply you with a list of the local variables involved.
I'm not sure I fully understand what he means since it sounds too technical for a person not experienced in aircraft modeling... like me. So, I decided to post it here in hope that you could comment on it in more detail. Btw, if you want to try the addon, you can download it from here: http://simviation.com/1/download-file?file=d75n1.zip
Thank you very much!
-
Thanks for your prompt reply!
Here is what I did following your advice:
********* FSUIPC, Version 3.989z by Pete Dowson ********* ... ... [Continuation log requested by user] Module base=61000000 WeatherReadInterval=4 LogOptions=00000011 LogExtras=1 119435 System time = 23/03/2011 04:04:41, FS2004 time = 00:27:39 (08:27Z) 119435 *VIS* SM: Min=0.00, MaxRny=0.00, MaxOvc=0.00, MaxCld=0.00, MaxClr=0.00, Upper=60.00, FT: LwrAlt=0, UppAlt=25000 119435 WeatherOptions set, now 4000B6A7 (timer=0) 119435 LogOptions changed, now 00000011 (LogExtras=1) 119513 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 119513 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 119513 AP READOUTS: Flags1=00000000, Flags2=00000000 123116 *** EVENT: Cntrl= 65560 (0x00010018), Param= 0 (0x00000000) STROBES_TOGGLE (NoAccel) 125566 *** EVENT: Cntrl= 65751 (0x000100d7), Param= 1 (0x00000001) LANDING_LIGHTS_TOGGLE (NoAccel) 127921 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 1 (0x00000001) TOGGLE_NAV_LIGHTS (NoAccel) 129169 *** EVENT: Cntrl= 66239 (0x000102bf), Param= 1 (0x00000001) TOGGLE_BEACON_LIGHTS (NoAccel) 130714 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 130714 .. Key not programmed -- passed on to FS 130932 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=1 130932 .. Key not programmed -- passed on to FS 130932 *** EVENT: Cntrl= 65749 (0x000100d5), Param= 0 (0x00000000) VIEW_MODE_REV (NoAccel) 131057 KEYUP: VK=83, Waiting=0 131899 KEYDOWN: VK=83, Waiting=0, Repeat=N, Shifts=1 131899 .. Key not programmed -- passed on to FS 131899 *** EVENT: Cntrl= 65749 (0x000100d5), Param= 0 (0x00000000) VIEW_MODE_REV 132024 KEYUP: VK=83, Waiting=0 132648 KEYUP: VK=16, Waiting=0 136205 *** EVENT: Cntrl= 65732 (0x000100c4), Param= 0 (0x00000000) EXIT (NoAccel) 136236 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=Y 137718 Flight saved #2 = "Previous flight" 138295 System time = 23/03/2011 04:04:59, FS2004 time = 00:27:57 (08:27Z) 138295 *** FSUIPC log file being closed Memory managed: 0 Allocs, 864 Freed ********* FSUIPC Log file closed ***********
And here is the extract from my FSUIPC.INI:
[Profile.Default] 1=D75N1 ; Boeing Stearman 2=Cessna Skyhawk 172SP [Buttons.Default] 0=R0,32,C65734,0 ; Pan forward 1=R0,33,C66416,45 ; Pan forward right 2=R0,34,C66416,90 ; Pan right 3=R0,35,C66416,135 ; Pan rear right 4=R0,36,C66416,180 ; Pan rear 5=R0,37,C66416,225 ; Pan rear left 6=R0,38,C66416,270 ; Pan left 7=R0,39,C66416,315 ; Pan forward left 8=P0,1,C65752,0 ; Parking brakes 9=R0,5,C65588,0 ; Brakes 10=R0,6,C65777,0 ; Mixture decrease 11=R0,7,C65775,0 ; Mixture increase 12=P0,0,C66240,0 ; Taxi lights 13=P0,14,C65751,0 ; Toggle landing lights 14=U0,14,C66240,0 ; Taxi lights off 15=P0,13,C65758,0 ; Flaps down incr. 16=P0,4,C65595,0 ; Flaps up all 17=P0,8,C66239,0 ; Toggle beacon lights 18=P0,9,C65560,0 ; Toggle strobe lights 19=P0,10,C66379,0 ; Toggle navigation lights 20=P0,11,C65750,0 ; Toggle panel lights 21=R0,2,Cx42000BC0,xC0010080 ;offset SWord value - elevator trim down 22=R0,3,Cx32000BC0,x3FFF0080 ;offset SWord value - elevator trim up 23=R0,20,C66277,0 ; Aileron trim right 24=R0,22,C66276,0 ; Aileron trim left 26=R0,21,C66529,0 ; buttons 26-31 for Eyepoint movements inside VC 27=R0,19,C66528,0 28=R0,25,C66525,0 29=R0,23,C66524,0 30=R0,26,C66527,0 31=R0,24,C66526,0 [Buttons] ButtonRepeat=0,10
As you can see, I use the same commands for lights both in the INI file and FSUIPC log. But looking at logfile, I suspect there is smth wrong, e.g.:
130714 .. Key not programmed -- passed on to FS
What do you think? Thank you!!!
-
Hi there,
I am lucky enough to fly this wonderful Stearman from Doug Kallen: http://simflight.com/2011/02/02/boeing-stearman-by-proptrash-a-new-record-for-fs2004-models/
The only problem I have is no matter what I do I cannot switch lights (nav, strobe, taxi, etc.) with custom joy button commands assigned in FSUIPC.INI. The same INI file works ok with other aircraft (e.g., default C172) when I put the value of "title=" from aircraft.cfg under my custom profile inside FSUIPC.INI (ShortAircraftNameOk=Yes). I do the same for Stearman and can pan view and move eyepoint (default FS9 commands/keys mapped to joy buttons) plus do a couple of other things through the same FSUIPC.INI in Stearman - just can't understand WHY only the lights are inoperable through FSUIPC. :(
Any advise is highly appreciated!!!
Vuqar
-
MF mesh is LOD10 (38m) mesh. FSG2010 uses LOD11 (19m) mesh covering USA and Canada nationwide. So, the question is WHERE in scenery.cfg FS GLobal mesh should be placed to in terms of priorities - above or down MF entries?!?
In my scenery.cfg FSG2010 is way under MF and Misty Moorings sceneries. Is that ok?
Thank you!
-
Is the switch for selecting the mode detected as a switch or button in FSUIPC? If so you simply make your FSUIPC assignments conditional upon that switch setting. If not then you'd need some other switch to act as the selector.
No, Sir, FSUIPC does not recognise the switch for sure! I guess I have to use one of the regular buttons, as per your advise. Question is HOW!?
How do you work that out? The condition test only determines whether that line, that assignment, should activate when the primary button/switch is used. That's why that assignment becomes "conditional". You make other assignments for the same primary button or switch with different conditions. Hence you get different modes. If you only have one condition button you only have two modes -- with the condition button or switch off or on. With multiple switches or buttons, or a multiway switch, you'd have 2^N modes (2 buttons --> 4 modes, 3 buttons -> 8 modes, etc).Sorry, I am quite new to FSUIPC and indeed very limited to try it in full since I use my friends computer (i.e., his registered software). Btw, I just checked Simmarket - it accepts Paypal and, thanks to your return and prompt reply FSUIPC3 is in my checkout box now... :)
Anyway, I have only manuals in hand and from what I understand the conditionality of buttons apply if one wants to trigger events which are connected to the primary event only - e.g., pressing the button at 50ft to change to ATC-required tower frequency would simultaneously trigger gears up, OR another useful example - after pressing the button to change radio frequency, button OFF would also make (swap) the standby radio to active mode. But there is a limited number of such conditions within the scope of activities in any aircraft. And that's why I cannot understand how the joystick modes can be changed with button on and off... Sorry, if I understood everything wrong from the manuals!
You can also use one button to make as many modes as you can, by using it to cyclically increment a user offset (Offset byte cyclic increment control). You can use User Offset x66C0. Then the condition you'd use would be an Offset test: "B66C0=0 ...", "B66C0=1 ..." etc. One Byte can have 256 values, so256 modes. The only trouble with that method is keeping track of which mode you are in. You could use a Lua plug-in to display that, however.Again, I cannot practice with offsets since I don't have FSUIPC yet. But the explanation within manuals seems rather vague to me, on the other hand. I'll put it simple - I even don't understand WHAT are they and how one can get use of 'em... I better go back to the manual reading. At least, you reassured me that there IS a possibility (I prefer the word "facility" the way you use it) to implement joystick modes in FSUIPC. The more I am in the "business", the more I like it!!!
All you need to do is set things up in cold and dark mode and save that as your default flight.I have done that already! I was just thinking of trying the same with FSUIPC - so deep I love these 300 kbs! :)
Thank you very much! And see you when I'm registered!
-
Dear Peter (and the Team?),
First off, I would like to seize this great opportunity to convey you my best regards and my ENDLESS thanks for such a nice software you developed - FSUIPC! Tbh, I'm speechless to see how expandable and versatile some 300Kb library file can be... A piece of art and an exemplary show-off for beginning programmers like me. Thank you very much for your efforts you put into the development in order to cherish the whims of flightsim fans, to say the least!
======================================================================================================================================
Straight to the deal... I've spent a couple of hours to read thoroughly the documents shipped with the FSUIPC - quite a steep learning curve but very fruitful experience, on the other hand! Please correct me if I am wrong, but from what I understood reading the Advanced Users' Manual, there IS a possibility to "program" (through INI file) different "flight scenarios" (takeoff, climb, descent, etc.) using a joystick with a bunch of buttons only. I currently use Saitek's X52 Pro which has some 40 clickable buttons, POVs, etc., and, to be honest, expandability (wow, I said that!) of FSUIPC was the very first question I've been asking myself before reading the manuals. Could you please show a quick example on how to assign conditional commands through FSUIPC, like changing radio frequencies for COM and NAV using one POV only:
COM Mode actions:
1- Changes COM2 (standby) with increments/decrements of whole and fraction numbers (four-button POV used: the first 2 buttons change the whole numbers the last 2 - the fractions);
2- When I'm happy, swaps COM2 to COM1 (compound buttons?!?)
NAV Mode actions:
1- Changes NAV2 (standby) with increments/decrements of whole and fraction numbers (the same four-button POV used: the first 2 buttons change the whole numbers the last 2 - the fractions);
2- Again, swaps NAV2 to NAV1 (e.g., on button release?).
One of the reasons I bought X52 Pro was it was possible to adjust it for three different Modes by switching the relevant knob on the stick. And I would definitely like and have some ideas to use FSUIPC instead of the regular Saitek's API to program it the way I like. But when I read Compound Buttons section of Advanced User's Manual, it didn't give me the idea of using the joy in different modes - only execution of secondary actions by triggering the primary action first! Although it is VERY useful facility but I couldn't somehow materialize how Compound Buttons conditions may be applied in shifting the joystick modes.
====================================================================================================================================
My other question will be similar to the one you've been asked before (see: viewtopic.php?f=54&t=13882). However, I'll put it in other way - is it possible to START (not restart!) a flight after selection of a proper aircraft (which has been made entries in INI file for) from FS Aircraft menu in a cold-and-dark mode, i.e. from the beginning of flight? You may say many addon developers like PMDG offer this possibility already but what about a default aircraft? But I have read in another thread that it was actually possible to apply this on PMDG JS41 using LUA programming language. The other reason is I currently use default C172SP "adapted" by RealAir Simulations and like the way it behaves both on the ground and in the air - huge difference with default one!
Well, once again thank you for your support and patience bearing this long post with me... :)
Rustam
LUA file and button / keypress assignments
in FSUIPC Support Pete Dowson Modules
Posted
Thank you, Pete!
I've followed your advice and this is what I have achieved so far:
FSUIPC.INI section:
Contents of the LUA file:
-- PARAMETERS -- ---------- -- 1 = Inertial Clutch Charge -- 2 = Inertial Clutch On -- 0 = Inertial Clutch Off -- Set to Zero ipc.writeLvar("L:AN2_inertial_clutch",0) -- Set to Charge if ipcPARAM == 1 then ipc.writeLvar("L:AN2_inertial_clutch",1) ipc.writeLvar("L:play_sound",11) end -- Set to On if ipcPARAM == 2 then ipc.writeLvar("L:AN2_inertial_clutch",-1) ipc.writeLvar("L:play_sound",11) end -- Set to Off if ipcPARAM == 0 then ipc.writeLvar("L:AN2_inertial_clutch",0) ipc.writeLvar("L:play_sound",0) endFilename: SW_AN2.lua.
The file sits inside FSX Modules folder. However, whatever I do I can't initiate the ipcPARAM == 2. Parameters 0 and 1 work and LVar "play_sound" plays as it should though.
Any guess what can cause the... problem?
Thanks!