Jump to content
The simFlight Network Forums

mr.crocodile

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by mr.crocodile

  1. Sorry Pete, my mistake, I was thinking RIGHT but I wrote LEFT. So on the right I have nothing. Ok, I just tested the configuration using a default aircraft and you are right, all seems to work great. So it could be a problem related with the IFly aircraft. Obviously it is a bad news, I hoped it could be an error on my configuration procedure but I think it is not the solution. Yes, the Saytek Proflight Yoke has a little USB hub with 3 USB ports and a PS/2 port at which connect the throttle quadrant with a PS/2 connector provided in the package (http://www.saitek.com/uk/prod/yoke.html). The additional Throttle quadrant I bought to have more levers, instead has a normal USB connector. This one seems to be affected by the problem I tried to solve till today. Anyway, I have to thank you for the time spent to explain me the situation. I will keep you updated in case I could solve the problem
  2. Ok, I tried again with the indication I found on your FSUIPC user guide where at page 41 (I have the guide dated 7th november 2006 for version 3.71 of FSUIPC.dll but I have version 3.999z9a installed on my FS2004) I read If you do calibrate with a centre zone, then the values from “minimum” (the left most value), or lower, up to the lowest of the Centre values will all select spoilers down (i.e. parked). The centre zone will arm the spoilers, and the range from the higher of the two centre values up to the maximum (the right-most value) will actually operate the full range from 0% to 100% deployed. So I have Axis Assignment page of FSUIPC Option and Settings. The Delta value is 256, I set Send direct to FSUIPC Calibration option and then I selected Spoilers from the drop down menu. On the left of the same page I have nothing. Then on Joystick Calibration page I went on the Spoilers (direct!) section, I pressed on RESET button and started again: REV checked, then I started from down detent position (full forward position) and pressed the first (on the left) SET button and I obtained -16383, then I moved the lever towards the ARM position and I selected the center SET button one time to obtain -8643, then I moved again till -5676 and then I pressed again the center SET button, then I moved the lever all way down (full back position) to obtain 16384 and then I pressed the right side SET button. Then I pressed OK and with my IFly 738 (version 3.2.1) at 20000ft 230kt I make some test moving the lever. This is the result: In the range from -16383 to -5676 (so both in the OFF and in the ARM zone) the lever does not move and remains fixed in the position you can see in the Clipboard01 When the lever exits from the ARM zone and enters the deployed zone the lever moves from the above position to the flight detent following the axis movement. (clipboard02, clipboard03) If I push back to down detent the axis, the lever does not come back to down detent position but stops where it was at the start of the test. I attach a couple of images to show you in case I was not so clear in my explanation. I would clarify that I configured an other axis for FLAPS using your guide and all works perfectly. Another note is that the configuration I explained in my last 19 February 2015 post, seems to work well using the throttle quadrant with PS/2 connector. The problem I noticed appears with the throttle quadrant with USB connector. Instead the configuration described just above in this post works bad even using PS/2 and USB throttle quadrant.
  3. Hi Pete, I discovered this old post and because of the fact I have a similar problem with the spoiler axis configuration I try to explain it hoping to reach a possible solution: I assigned the Y axis of my throttle quadrant to the function of Spoiler lever. I went to Axis Assignment page of FSUIPC Option and Settings. The Delta value is 256, I set Send direct to FSUIPC Calibration option and then I selected Spoilers from the drop down menu. Then I set a range to configure the Spoiler OFF (down detent position) and a range to configure the Spoiler Arm. So the range 1 is FROM 9729 TO 16383 with UP and DOWN option checked, and the control sent when range entered is Spoiler Arm Off (parameter is left to 0). Control to repeat whilst in range and Control sent when range exited are unchecked. The range 2 is FROM 5120 to 9728 with UP and DOWN option checked, and the control sent when range entered is Spoiler Arm On (parameter is left to 0). Control to repeat whilst in range and Control sent when range exited are unchecked. Then in the Joystick Calibration page 6 in the Spoilers (direct!) section I have the following parameters: Filter is unchecked, Rev is checked, -5119, -512, 16384 and the second center set value is again -512, Slope is 0. So I think that all the range is covered with 3 zones without any overlapping. The problem is that when I move the axis inside the Spoiler Arm zone in some cases (more or less ramdomly) the spoiler lever moves in the ARM position and immediately come back to DOWN position. If I move repeatedly in some cases the lever stops in the ARM position but not always. Did I make some mistake configuring the axis?
  4. Hi Pete, sorry if I write my feedback so late from my last post. I "studied" better the situation about the OFFSET 1400 (thanks to another post of yours I found searching in Internet) and so I wrote down a LUA script with which I solved my problem to update fuel and payload without closing FS9. In the LUA script I added a little code to quickly open FS payload menu and OK out (as you stated in your last post) and in this way I obtained the result I was searching for. The LUA script is generated by a macro into the Libreoffice spreadsheet with which I simulate and calculate the payload of my aircraft. So thanks for your help and sorry if my english could be not so good...
  5. Thanks Pete, the "Reload Aircraft" FS control works well but not in the way I need. So I'm trying to create a .lua plugin. For the fuel I solved, the .lua plugin read the fuel quantity from a text file and then transfer it to FS using the appropriate OFFSETs. Now I have some problem to make something similar for the payload. I do not understand how to use the OFFSET "1400" related to the payload stations. I started trying to read and write it to a csv file (using the example you included in the "Example LUA plugins.zip" to understand how it is made, but I obtain only one number. The FSUIPC4 Offsets Status (I hope this document is usable also with FS2004) talks about payload stations so I expected to obtain a number of values from this OFFSET. What did I misunderstand? In the same document seems to understand that it should be possible to modify the loadings of this offset, but using FS-interrogate on that offset, I noted that this is a READ only offset. Hope you could enlighten me a little bit more Thanks and Merry Christmas Andrea
  6. Hi all, I created a spreadsheet (using LIbreOffice) with a macro to simulate the passenger and cargo loading aboard the aircraft. After I inserted the number of pax, the number of baggages and the fuel quantity, the macro simulate a random distribution of the pax aboard and the positioning of the baggage into the cargo holders of the plane following some company rules. After that, the spreadsheet calculates the longitudinal and lateral harms (from the datum) of the payload (pax and cargo) in function of its position inside the aircraft (I used a certain number of stations to consider the seat rows and cargo holders). At the end, the spreadsheet, using another macro, generate the aircraft.cfg file and save it inside the FS2004 aircraft folder to be used at the moment the aicraft is loaded into the simulator. In this way I obtained a precise position of the CoG of the aircraft simulating in a very realistic way the payload aboard. Now the only problem for this system is that between one flight and another, to update the aircraft.cfg file with the new payload, I need to exit the flight and reload the aircraft after generating the new aircraft.cfg file by the macro. I noticed that some ACARS distributed by some virtual companies (for example the VCRS by Ryr Virtual), give the possibility to load the payload using FSUIPC. So I discovered that there are some offsets that allow to work with the payload station values. I'm not a programmer and it would be very difficult for me to create an application to do this, but could it be possible to create a macro for my spreadsheet that, working in combination with FSUIPC , could give the possibility to update the payload station variables (weight, lateral, longitudinal and vertical distance from datum) and the fuel instead of creating every time a new aircraft.cfg file? Thanks in advance for any suggestions
  7. Thanks Pete, I'm going to try. Maybe it is my mistake because I did not recognize that 3.999y5 is after 3.999w and I did my registration 3 days ago so I need to follow the indication you posted on the first highlighted message in the forum. This evening I'll do the test. Thanks
  8. Hi Pete, sorry to bother you but I have a concern about FSUIPC that seems to be the cause of malfunction of my new saitek proflight yoke. I just installed my registered copy of FSUIPC 3.999w but in the IFLY cockpit the PFD and ND indication are that the version of FSUIPC is old or illegal. What I need to do? I register and paid using the following data: Andrea Nardi Order 964079 I noticed that if I use the older 3.82 version, without register it, the PFD ND panels work correctly, if I registister that version with the same data the problem appears again. Maybe it could be due to the registrazion code? I hope you could help me Thanks Andrea
  9. Hi Pete, I just installed my registered copy of FSUIPC 3.999w but in the IFLY cockpit the PFD and ND indication are that the version of FSUIPC is old or illegal. What I need to do? Andrea Nardi and registration Order 964079 Thanks Andrea EDIT: I noticed that if I use the older 3.82 version, without register it, the PFD ND panels work correctly, if I registister that version the problem appears again. Maybe it could be due to the registrazion code?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.