Jump to content
The simFlight Network Forums

simnutzer1962

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by simnutzer1962

  1. I love England. In my youth I was often there. Most times in Bournemouth and London. Had friends there. And I had some shows in London Luton. Two years ago, I made Holidays in Endinburgh for one week. I know, it is Scottland, but it belongs to UK. Last year I had been there again, for the Military Tattoo. It was wonderful. It`s a mess, that UK left the EU.
  2. In Spain. That is a beautiful country. Where are you born? In the USA? The name John Dowson sounds american.
  3. Hi John, I am amazed. What a great job. I am a professional magician here in germany. But in two years I will retire. I will give a 5 from 5 Star review. I will do that tomorrow, cause in the moment I have no access to the simmarket. If I had known, that you speak and write german, I had written my posts in german πŸ™‚ πŸ™‚. You write, that you have lost the biggest part of your abilities to speak. I can give you some lessons for free, if you want. I live about 100 miles north from Darmstadt.
  4. Ok, I will do my best in future. Kind regards, Robert
  5. John. You make me happy, again. Now it works all well. I post the FSUIPC.ini again, that you will have it for your records. May be other fellows here may or will have the same problems, which are now solved. Would you be so kind to explain to me, what the particular values in this sample lines mean? It is for my basic understanding. CR(+1,11)1,14 C66587,38408 -{ROTOR_BRAKE}- Thanks a lot. FSUIPC5.ini
  6. I was testing something. But I erased the control sets in P3D. As I mentioned, it works now very well.
  7. Man, you made my day in case of the levers. With your suggestion to send directly to the FSUIPC calibration, it works perfect. I reversed the levers in the cali9brationsection of FSUIPC and the levers work also in the right directions, now. THANK YOU SO MUCH!!!!!
  8. Dear John, thanks for asking. No, I did not manage it. I have to lack knowledge and understanding, how this all works. And because my understanding of English is not exactly good either. It takes me hours to fight me through the words to understand the instructions. And additionally I am a kind of "leghastnic" πŸ™‚ πŸ™‚ in computerlanguages and I would really appreciate your graceful help. FSUIPC5.ini
  9. Hi John, unfortunately nothing from your suggested procedures works. Though I put the function of the Flapssetting to a button, it does not work, too. I thought, that the thrustmaster could be defect. I tried another Joystick and the result was the same. No Button and no axis let move the Flaps in the sim. So it can not be the Thrustmaster itself, I think. What`s interesting is, that only the thrustlever works fine in FSUIPC. If I switch on the controls in the P3D controlsection, the Spoilerlever works fine, and the Flapslever does work for Flaps 1 to 30, but does not work for Flaps 0 and Flaps 40. This is all strange. I think, I have to contact PMDG for Support.
  10. Hi John, sorry for the circumstances. Indeed, I forgot to switch off the controllers inner P3D settings. I switched them for the axis on all existing hardware to off, now. So the throttlequadrant levers are controlled only by FSIUPC, now. But they do not move at all. I proofed all my calculations for the values belonging to the Flapslever and I can not find any wrong calculations. And in the SDK for the PMDG 737 I couldn't find any other values than the ones I calculated with. For your information and to check my calculations, written down in the FSUIPC ini file by setting them via FSUIPC. Here is an extract of the values from the sdk file: // Control Events #ifndef THIRD_PARTY_EVENT_ID_MIN #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 #endif #define EVT_CONTROL_STAND_FLAPS_LEVER (THIRD_PARTY_EVENT_ID_MIN + 714) #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 7141) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 7142) #define EVT_CONTROL_STAND_FLAPS_LEVER_2 (THIRD_PARTY_EVENT_ID_MIN + 7143) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 7144) #define EVT_CONTROL_STAND_FLAPS_LEVER_10 (THIRD_PARTY_EVENT_ID_MIN + 7145) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 7146) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 7147) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 7148) #define EVT_CONTROL_STAND_FLAPS_LEVER_40 (THIRD_PARTY_EVENT_ID_MIN + 7149) If needed, I can send a screenshot of my FSIUPC Windows from the axis settings by wetransfer. Dear John, I am so sorry for my lack of knowledge to get everything working properly. And I am very grateful for your patient help. Best wishes Robert FSUIPC5.ini FSUIPC5.log
  11. Hi John, thanks for answering. I will do that tomorrow, cause it`s 11 o clock in the evening here, now and I shut down the computer. But one question: In the case of a to big datafile: On which mailadress should I send the datafile? Wetransfer or filetransfer need a mailadress. I can send it also directly to a mailadress, cause a regular mail size could be up to 30 Mbytes and the file has in the moment roundabout 6 Mbytes. But we will see tomorrow, wheather your tips let shrink the size of the datafile. However. I have to go to bed now. Sincerely Robert
  12. Hi John, this time I just switched on the logfunctions you mentioned and began to operate the lever. I erased the rotor brakes by hand, cause the "Don`tLogThese" did not work in case of the fact, that I did something wrong. But I can not upload the file, cause the compressed file is still more than 6 Mb and it is only allowed for me to upload files till a maximum size of 4.88 Mb.
  13. Ok, I will do that later, cause I have to do some sports now. My doctor tells me that πŸ™‚. What do you mean with a "full" logfile?
  14. It did not help. Problem still exists. I attached the inifile and the logfile. This logfile is full of confusing lines and I have no idea, why are so many lines with the terminus "Rotor Brake" is in that file. FSUIPC5.ini FSUIPC5.zip
  15. I am programming the FSSUIPC5 for my PMDG NGX for P3D. And I have a problem. I wanted to control the flaps by a Joystickaxis. For this I did following things: Opened the PMDG SDK, where I found the following infos about the Flapslever: #define EVT_CONTROL_STAND_FLAPS_LEVER (THIRD_PARTY_EVENT_ID_MIN + 714) #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 7141) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 7142) #define EVT_CONTROL_STAND_FLAPS_LEVER_2 (THIRD_PARTY_EVENT_ID_MIN + 7143) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 7144) #define EVT_CONTROL_STAND_FLAPS_LEVER_10 (THIRD_PARTY_EVENT_ID_MIN + 7145) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 7146) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 7147) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 7148) #define EVT_CONTROL_STAND_FLAPS_LEVER_40 (THIRD_PARTY_EVENT_ID_MIN + 7149) In case of these values I calculated the Custom Control values by adding the basicvalue 69632 Then I started FSUIPC and opened the axis assignment. I moved the Lever on the joystick and began to create Step 1 by setting the numbers for "from" and "to" via moving the lever to different values. So I clicked "from", moved it to the second value and clicked "to". In the first case the values were from 16383 to 16180. After that, I used the function "Custom Control" to put in the value, I calculated fΓΌr the "Flaps 0" Position. In this case it was the value 76773. I did not write any value in to the Parameterline. The 0 are the defaultvalue inside the Parameterline. Then I repeated all the things, I did for further 8 steps. Here ist the Code, I found in the FSUIPC.ini, after i programmed FSUIPC in this way. The Pollinterva ans the RangeRepeatRate were automated set from FSUIPC. [Axes] PollInterval=10 RangeRepeatRate=10 0=1R,256 1=1R,B,16383,16180,76773,0 -{ Entering=Custom control: <76773> }- 2=1R,B,11663,13316,76774,0 -{ Entering=Custom control: <76774> }- 3=1R,B,5702,8593,76775,0 -{ Entering=Custom control: <76775> }- 4=1R,B,2386,4604,76776,0 -{ Entering=Custom control: <76776> }- 5=1R,B,-247,1601,76777,0 -{ Entering=Custom control: <76777> }- 6=1R,B,-3306,-1068,76778,0 -{ Entering=Custom control: <76778> }- 7=1R,B,-7128,-4410,76779,0 -{ Entering=Custom control: <76779> }- 8=1R,B,-13081,-9721,76780,0 -{ Entering=Custom control: <76780> }- 9=1R,B,-16384,-15748,76781,0 -{ Entering=Custom control: <76781> }- The problem is now, that the Flapslever in the Sim does not move to the Flaps 40 position as ist should move, programmed in number 9 of the steps and it does not move to the Position Flaps 0 (what means Flaps up, I think) and stops at the Flaps 1 Position. It seems so, that Step 9 and Step 1 will be ignored. The Lever stops at Flaps 30 and at Flaps 1. Where is my mistake? Thanks a lot.
  16. Thnks again, Pete. I care later about it. Now I care about the things. that I can manage, in the moment.
  17. Thanks for your answer and the advice to use a luascript. I am not more familiar with the scriptlangauge. And I must learn it again. Then I will see, what I can do later. Seems to me, I have to use Linda in the meanwhile and to get a PMDG datafile for it. I like to work with the pure FSUIPC much more. But anyway. One step after another. It is really amazing, how fast I have forgotten so many things.
  18. Hi Pete. In case of healthproblems I have been away a few years from the Flightsimulator and now I am back. I had sold all my stuff, cause it was not clear, what happened to me. And so I have not one byte of data from my old computer, which is gone, where all my collected knowledge was stored. And time has gone and I forgot all my knowledge I had and now I try to get in again. I still use P3D 4.5 and work with FSUIPC 5. And I was seraching for the solution of the Thrustmaster Boeingthrottle problem, which is described here. I bought it used via Ebay. Due to the fact, that my English is quite rusty (I need a lot of time to formulate the sentences and the same time to understand, what is written here), I am not really able to understand all the information in this thread, to solve the problem, the fellow had, too. I do understand, that I need the custom Controls for operating the upper knob on the rotary switch and the rotary switch itself, but I can not find the solution, how to progam them via FSUIPC. What I did is to log the events. And the log shows me following information: FirstButtonChange res=0000010F (0.1, 15) - It`s the result to turn the "Sel knob" to the right. FirstButtonChange res=0000010E (0.1, 14) - It`s the result to turn the "Sel knob" to the left. If I turn the "Rotary switch" iteself to select the IAS/Mach, the HDG/TRK and the Altitude, it shows the following results: FirstButtonChange res=0000010B (0.1, 11) - It`s the result to turn the "rotary switch" to IAS/Mach. FirstButtonChange res=0000010C (0.1, 12) - It`s the result to turn the "rotary switch" to HDG/TRK. FirstButtonChange res=0000010D (0.1, 13) - It`s the result to turn the "rotary switch" to Altitude. If I push the "Sel-knob" it shows the following result: FirstButtonChange res=00000110 (0.1, 16) I understand, that the last numbers from 11 to 16 are the numbers of the buttons, cause they all are representing just a push of a button. I think, that the numbers 0 and 1 are representing the states 0 for off and 1 for on, in case of the fact, that a switch or button can only have this two states. I assume, that the line of numbers with the B,C and D at the end of the long number must be hexadecimal numbers. I calculated from the PMDG SDK the numbers I needed to trigger the right operations. For example the 70022 for the headingselector (calculated by adding the basicnumber 69632 and the 390 for the Headingselector in the MCP Section of the SDK Data). But here are my problems, I have no idea, how to combinate my knowledge to make the "rotary knob" and "the sel knob" work proper by programming in FSIUPC. For example: I open FSUIPC and go to the Button/Switches menu. Within I switch the rotarybutton to HDG/TRK and it shows me the Joy 1, button 12. In the "Control send" I choose "Custom control" and put in the mask my calculated 70022. And now my struggeling begins. What value to put in the parametersection? 0 or 1 do not work, and if I put the value for the left mousebutton "536870912" it only changes the indicator one time and turning the sel knob does not work, in case of the fact, that I am not able to program it for three different selectors. I think, that I am totally on the wrong road, cause I can not imagine, how to combinate those things. So I need advice to solve my problem. Thanks for the helping hand.
  19. It works!!!. Thanks a lot. Have a nice weekend. best wishes Robert
  20. thank again, John for your help, again. I will try it tomorrow. It`s evening here, now and or daughter is come visit us. I will give feedback, as soon as I can try this possibility. Best wishes Robert
  21. Unfortunately I must ask again. I did all the things you ordered to me and laid the Flaps Set Function to different Function Buttons on the keyboard. I emphasize, that I have no other functions over the P3D control menue on the Function Buttons. But two things happened. 1. When I move the Flapslever only on every second step (Flaps 1, 5, 15, and 30) , the value is shown, which I can set as the paramater value in the "keypressmnue" of FSUIPC. 2- It does not matter, wheather I put the shown value in the Parameterline. Nothing happens then with the Flaps. They do not move, if I press the Functionbutton n the keyboard. Must doing something wrong. Any ideas? Best wishes Robert
  22. Hey Man,thank you so much. That would be helpful. I will do my best and hope, not bother you again, in case of this problem. Sincerely Robert
×
×
  • 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.