Jump to content
The simFlight Network Forums

ark1320

Members
  • Posts

    609
  • Joined

  • Last visited

  • Days Won

    14

ark1320 last won the day on January 11

ark1320 had the most liked content!

1 Follower

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA

Recent Profile Visitors

2,854 profile views

ark1320's Achievements

Community Regular

Community Regular (8/14)

  • Posting Machine Rare
  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

28

Reputation

  1. I added ignoreDevice=0xFFFF,0xFFFF into the [Joy Names] section of the FSUJIPC7.ini file and then reran the FSUIPC7.7.4.12 installer and started the sim. The Fulcrum yoke worked. BTW, the Logitech joystick was not plugged in, so that's why it was "missing". Al FSUIPC7.ini FSUIPC7.log InstallFSUIPC7.log
  2. John, The above FSUIPC7.exe file you posted has fixed the Fulcrum yoke issue for me. Thank you. Does this give you the info you need, or would you still like me to go back and reinstall ver 7.4.12 and then insert IgnoreDevice=0xFFFF,0xFFFF into the [Joy Names] section of the FSUJIPC7.ini file to see if that works also? Al
  3. For some reason the latest version of FSUIPC7 will not recognize my Fulcrum yoke, so the FSUIPC7.ini file shows "Missing Joystick". I have had this yoke for well over a year and this has not been a problem before. If I use an older version of FSUIPC7.exe the yoke works as expected. The FSUIPC7.log file shows this: 422 Product= Fulcrum One Yoke 422 Manufacturer= Vitaly [mega_mozg] Naidentsev 422 Serial Number= MMJoy2-Fulcrum-03 422 Vendor=0000, Product=0000 (Version 0.1) 422 **** Ignoring device with VendorId=0000, ProductId=0000 **** What suddenly trigger this type of problem? Older log files show the Vendor and Product 0000 Ids did not cause a problem. The complete FSUIPC7.log file is below. Thanks, Al FSUIPC7.log
  4. Hmm... Interesting, I have been installing FSUIPC7 there for years without a problem. Until today I did not realize there were install options between using MSFS .bat and the EXE.xml file. I guess previously the installer defaulted to the EXE.xml option which I use, but now defaults to using the MSFS.bat file. I only included my MSFS.bat file above because I saw you had requested it from a previous poster -- I didn't realize that was an install option. So I have selected the EXE.xml option and all is working now, thanks very much for your help. Al
  5. HI John. I can't get FSUJIPC7 to autostart after installing ver 7.4.12. There is no FSUIPC7 entry in my exe.xml file. MSFS.bat attached. Thanks, Al MSFS.bat
  6. An exclamation point at the start of a line also works to indicate a FSUIPC7.ini file comment, for example: ! PY,1,C66289,0 -{SYNC_FLIGHT_DIRECTOR_PITCH}- no longer used I have been using the ! to comment FSUIPC.ini files for years, but now can't find a reference to it, and don't know where I first saw this. 🤔 The # stands out better than the ! so maybe I will replace all the ! with # to comment out whole lines, and use the ; just for inline comments as I do now. Thanks for the info, John. Al
  7. Generally, Avars and Lvars require the > only if you are trying to write (store) a value into them. K events do usually have a > before the K. In this case I think of the > as meaning "activate" the event. Sometimes, but NOT in presets or calculator code, the > symbol will be replaced with > meaning "greater than". I'm not sure what the 60 represents in the above, but note that one radian is about 57.29 degrees, so 10 degrees is about 0.17 radians. Also, often you can change the units a variable uses, so you may be able to write the Avar (A:ELEVATOR TRIM POSITION, radians) as (A:ELEVATOR TRIM POSITION, degrees) which may be more convenient in your particular application. Al
  8. Some observations: 1. Min and Max should be min and max. 2. According to the SDK, the value of (A:Elevator Position, number) goes only from -16K to 0. 3. Given the range of (A:Elevator Position, number) above, unless the Elevator_Angle_Trim value is less than - 16255, (L:Elevator_Angle_Trim, number) 128 - -16383 min will be -16383 and then you are putting that into (A:Elevator Position, number). It will then get more negative from there when the preset repeats and it seems you will almost immediately exceed the negative range of (A:Elevator Position, number). Don't know if that is OK. 4. Given the range of (A:Elevator Position, number) above, (L:Elevator_Angle_Trim, number) 128 + 16383 max will be 16383, and then you are putting that into (A:Elevator Position, number) which supposedly has a max value of 0. And the value you are putting into (A:Elevator Position, number) will get more positive when the preset repeats. Don't know if that is OK. 5. It would seem the Lvar (L:Elevator_Angle_Trim, number) located after the Min and Max operators is missing a > before the L: (unless I misunderstand what you are trying to do). 6. I have some timing concerns about trying to update an Lvar and them immediately using the new Lvar value in the next operation in the same preset. I would have to test that to see if it would work reliably. 7. While the presets are updating the value of the Avar (A:Elevator Position, number), I assume the sim might be doing that also, so how the dual updating will work is not clear to me. Any needed corrections to the above are welcome. Al
  9. Johm, Above worked for me, tried it 3 or 4 times. Question: If at some point auto-tuning doesn't work and values are set manually for the startup parameters, the next time FSUJIPC7 starts will those manually set parameter values be over written by the auto-tuning, or does the auto-tuning code check the FSUIPC7.ini file for those parameters? Thanks, Al
  10. Yes, that's what I meant by the current com freq spacing (channel spacing) -- 8.33 or 25 KHz. Thanks, Al
  11. John, When and how are offsets 0x0B47 and 0x0B48 updated in order to indicate the current com frequency spacing? Is there a way to force those offsets to update? For example, GPS units often "contain" the Com radios, and you can select the number of frequency digits to be used. If after loading the plane you switch the number of frequency digits, do you have to manually update offsets 0x0B47 and 0x0B48? Thanks, Al
  12. My understanding is Presets have to be one line, but can be a long line. If you want to use a toggle K event like TOGGLE_TAILWHEEL_LOCK, you typicality do not write a value into such K events since executing the K event actions the toggle function. It may be that simply using an Lvar in a preset in effect defines the Lvar. I seem to recall that being the case with calculator code, so maybe similar for Presets. I"m still not sure what you are saying here. But if you want to toggle the value of an Lvar between 0 and 1 each time a key is pressed, then one way to do this is to assign that key to a Preset similar to: MyPresetToggleName#(L:myLvar, bool) ! (>L:myLvar, bool) Then each time the preset is executed ( the key is pressed) the value of the Lvar will toggle between 0 and 1. I think the initial value of the Lvar will be 0 (and not undefined), but I would have to experiment a bit to confirm that. If it turns out the Lvar is undefined, then you would need to create and initialize it elsewhere before using the preset. Al
  13. I'm sorry, but I don't understand what you are trying to do with the mini-keypad, but perhaps I can help a little until John is available. 1. Yes, the MSFS SDK defines Bvars as input events. 2. looked at your myevents.txt file a bit and would like to mention a few things I don't understand. Just for example, consider the entry: C510_ATC_2#(>(A:TAILWHEEL LOCK ON, Bool) 1 == if { (>K:ATC_MENU_2) 0 (K:TAILWHEELOCK) } i. Why is there a > in front of the Avar (A:TAILWHEEL LOCK ON, Bool)? You would put a > in front of the A: itself if trying to write a value to an Avar, but the SDK would have to say it was a writeable Avar (although some Avars are writeable, most are not). In this case it does not seem you are even trying to write to the Avar at all. ii. It looks like you are trying to put a value of 0 into a K event called (K:TAILWHEELOCK). If so, you would need a >in front of the K: (in fact K events routinely have a > in front of the K:). But in this case I cannot find a K event called TAILWHEELOCK in the SDK. Where did you find that K event? I did find a K event called TOGGLE_TAILWHEEL_LOCK. If I'm off base here, sorry and please ignore! Al
  14. Easy enough to try I would think. Based on your log post above, it took 100 sec for FSUIPC7 to connect to SimConnect after you manually started FSUIPC7. For that particular test did you wait until MSFS had fully loaded (whatever fully loaded means) before manually starting FSUIPC7? Seems like you could run some experiments to see at what point starting FSUIPC7 manually works reliably for your setup. If FSUIPC7 doesn't connect to SimConnect, manually exit FSUIPC7 and then after 5 or 10 seconds simply manually restart it again. That has worked for me in the past. However, I still think using the FSUIPC7.ini parameters as John has outlined above is the best long term solution. That approach has been working reliably for me. Al
  15. Very sorry John, edited my post so it is correct now. Al
×
×
  • 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.