Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,231
  • Joined

  • Last visited

  • Days Won

    270

Everything posted by John Dowson

  1. The SU10 beta has been updated with several improvements, although there are still issues with some axes controls. See the announcements for the latest betam and the following thread for SU10 axis issues: John
  2. The latest beta release contains several improvements in the loading and availability of lvars. See John
  3. The desktop icon is an optional feature that just displays a splash screen while MSFS is starting, nothing more. If you don't use that to start MSFS, delete it and when you run the installer, uncheck the checkbox on the final page. If you want a shortcut for starting FSUIPC, just create one. There should be no issues starting WideClient while MSFS is in the main menu, but it will/may not connect (it may sometimes though). Always wait until you have an aircraft loaded and are ready-to-fly before reporting any connection issues. As I keep telling you, you can tell when WideServer is running by the MSFS title bar. But there is really no point in starting WideClient until you have an aircraft loaded. John
  4. Another update: FSUIPC_WAPID.dll I am also now going to release 7.3.9h....done - see Announcements.
  5. I have not updated the WASM zip file yet as I have still not released this. Currently its available in the latest beta download, in the SDK folder, so you will need to download this to get it for now - or use the attached: FSUIPC_WAPID.dll FSUIPC_WAPID.h
  6. There is an issue with lvars not being loaded when you restart the same flight that I am looking in at the moment...for now, you could try setting StopWAPIInMenu=No in the [General] section of your FSUIPC7.ini - but I think this also has issues in certain situations... I will post a new release once this is resolved. John
  7. Ok, then specific to the Fenix... That is what I thought, but thanks for confirming...I tend to forget these things.... Good - should be better in the next release, without the need (or much need...I will still keep it for a while...) of the LvarScanDelay ini parameter.
  8. Maybe Paul's dll needs to be rebuilt with the latest WAPI libs (not sure if you need to do this or just drop in the update WAPI lib or dll - ask Paul), or you need to rebuild your software using these. There have been some major changes in how the WAPi works in this release...anything that uses the WAPI will need to be recompiled with the latest libs. John
  9. Great! That depends if I update again before release...best to wait and recompile on release just in case.
  10. Ah, great...including the toe brakes fully functional? What about with the latest beta I posted above - can you check with that to see if that makes a difference please. John
  11. But there is no desktop icon to start FSUIPC7 - there is only one to start MSFS...so that will be why it doesn't start. That is the connection to MSFS, not WideClient/WideServer. WideServer status is reported in the MSFS title bar when running, not in the FSUIPC7 title bar. Do you have an aircraft loaded and ready-to-fly? Sometimes WideClient is started earlier, but other times only once you have a plane loaded and ready-to-fly, so check that you are in this state - and the MSFS title bar should indicate that WideServer is running and waiting for connections, as well as your FSUIPC7.log file with the following line: The log file you posted earlier shows that WideServer was not started as you never loaded an aircraft, and you exited after 23 seconds. Please load an aircraft before you try to do anything with WideServer/WideClient, and check that WideServer is running, either from the MSFS title bar or the log.
  12. The Axis Left/Right Brake set controls are no longer working in SU10, and as that is what the offsets use, that will be the issue. There is nothing I can do about this at the moment ecept report to Asobo/MSFS. Sorry about that. @AgniparvataThis is not quite correct....I had the parking brake set when I was testing...duh! I now do see some movement. However, it seems like the Brake Right/Left Position now go from 0-32767 and not 0-16383. I have updated for this in the attached version if you would like to try it. If you still have issues with this version, could you add FSUIPC monitoring of those offsets (0x0BC4 and 0x0BC6) and show me an FSUIPC7.log file where you apply the toe brakes. Also, please let me know what/if you are using those ini parameters, AxisCalibration set to Yes, or DirectAxesCalibs set to Yes or All? Also, check you FSUIPC7.ini and if you see any LeftBrake or RightBrake entries under your [JoystickCalibration] (or profile equivalent, if using) section then please remove those and try again - it seems that these are sometimes left even if the calibration is removed (I will look into this). John FSUIPC7.exe
  13. WideServer.log? No screenshots earlier that i can see, but not needed anyway. John
  14. Files? However, I won't get a chance to look at this in detail for at least a few days (too many problems with the latest MSFS release...), but if you can attach all your files (i.e. all logs and inis) then I will take a look when time permits, to see if I can determine what is causing this issue - although it may have resolved itself again by then...! John
  15. The Axis Left/Right Brake set controls are no longer working in SU10, and as that is what the offsets use, that will be the issue. There is nothing I can do about this at the moment ecept report to Asobo/MSFS. Sorry about that. John
  16. The ipc function is working correctly - as I said, try listing the lvars to see if those are available: S_OH_EXT_LT_LANDING_L and S_OH_EXT_LT_LANDING_R Reading lvars should have been ok with SU10, it was the writing/updating that was broken - and fixed in the latest beta 7.3.9f. That offset still uses the lvars read from the WASM, so I can't see how switching to using the offset would make a difference... the lvar has to be available to FSUIPC via the WASM however it is read. Ok, thanks. I don't have the Fenix, so cannot check the available lvars here. Thanks @Fragtality
  17. @Agniparvata Do you have ini parameter AxisCalibration set to Yes, or DirectAxesCalibs set to Yes or All? Those offset use the Axis Left/Right Brake Set controls, so I will check them here (both with and without calibration, and via the offsets). However, please note that those controls (and therefore offsets) no longer provide a linear brake axis (if it was working!). From the documentation: There are new linear brake axis control, but unfortunately these are not currently accessible/useable via 3rd party apps (SimConnect). I will raise a bug report for this, and once added I will switch to using these linear controls, or maybe add a new ini option so the user can decide which should be used (via the offsets). John
  18. This folder is created by P3D and is the location of the add-on.xml file. It should be used for that only, and you should not install the application into this folder. Its ok to leave it there if its working ok.... Cheers, John
  19. This is a known issue since the SU10 update that I am looking into. For now, you should only calibrate if assigned with 'Direct to FSUIPC calibration'. If assigned as 'Send to FS as normal axis', you need to delete the calibration for the axis. See the following thread for further details and where I will post any updates / new information on this issue: John
  20. There was a known issue swapping COM2 and NAV1 and NAV2 frequencies in that version. Can you please update to the latest beta (7.3.9f) and try again - if you still have issues I will need to see your FSUIPC7.ini and FSUIPC7.log files. See John
  21. That is strange...there is a FAQ entry on MSFS auto-start issues, but if this is an occasional issue I don't think it will help... That is even stranger...do you get any errors, or anything in the event log when this happens?
  22. For many tears the Modules folder was the default (and only) installation location. This was a hangover from the FSX days / FSUIPC4, which still uses that folder. No - I recommend that you don't install under the FS/P3D folder any more. This can also cause issues, depending on where the FS is installed. These days, it is better to have all your add-ons installed in a separate non-windows protected folder , such as C:\FSUIPC6 or C:\P3Dv5 Add-ons\FSUIPC6. The former is actually now the default installation location, but initially it defaulted to the location of the add-on.xml file, under your Documents folder, and when you re-install it always defaults to the existing installation location. John
  23. Ok - I will take a look at those... Ok, thanks for the update. Thanks.
  24. Can you set axes logging, open the console window, turn the elevator trim and tell me whet controls/events you see? Also check the elevator trim calibration, but I can't think how that could do this.... And maybe double check your assignments (or show me your FSUIPC7.in) to make sure its not assigned to both axes... John
  25. For this issue, can you also check and remove any calibration (that may still apply if using scripts), as well as using the latest beta. If its still an issue, I will need to see a log and the script you are using.
×
×
  • 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.