Jump to content
The simFlight Network Forums

Pete Dowson

Administrators
  • Content count

    33,625
  • Joined

  • Last visited

  • Days Won

    105

Pete Dowson last won the day on February 1

Pete Dowson had the most liked content!

Community Reputation

177 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Travelling, Real / Craft Ale,, worldwide

Recent Profile Visitors

24,175 profile views
  1. Hi folks, Sorry, but I'm away on holiday with my good wife until the 20th February. Please help each other as usual whilst i'm away. Regarrds Pete
  2. Hi folks, Sorry, but I'm away on holiday with my good wife until the 20th February. Please help each other as usual whilst i'm away. Regarrds Pete
  3. Please do read the title of a thread before appending completely unrelated support questions to it! I could have easily missed your post! You should have started your own thread with an appropriate title. I've left your post and my reply here for now so you can find it, but I will split this off later and put an appropriate title on it. You'll need to find it via your name. This thread will be locked now that FSUIPC 5.123 is released as that gives an explicit error message if you are not using P3D4.1 or later. "Does not install". What exactly does that mean? What is the symptom, an error message, or what. An Install log is always produced. You need to show that. And you say "as before". Do you mean you are re-installing FSUIPC5, or what? Check that you are using a supported version of FSUIPC -- 5.123 or later (current is 5.123c). The "LM software" being what? P3D or something else? I can't really help without information. Post the Install log, and also the FSUIPC5.LOg. Both files would be in the P3D Modules folder. Pete
  4. Some Issues of The Axis Assignment

    Yes, correct. Ah, okay. Thank you. You made me think you weren't looking there when you talked about the sim assignments being seen. This is strange, as from the logs and CSV you supplied, it has clearly been detected and should read the values okay. And I assume the other detected devices are showing values okay? What about buttons on the device -- are they detected? Pete
  5. It has got to be eiither bad weather data (but that usually crashes the simulator), or bad AI Aircraft textures seen in that area (but again you'd expect the same). Of course, it the end it could be down to any sort of corruption withing the simulator caused by bad data in that area. FSUIPC itself is certainly not aware or nor cares about where in the world you are. It's also unlikely to be only affecting FSUIPC, though that might be the more noticeable effect. If SimConnect is doing strange things that could affect almost any add-in or add-on. FSUIPC is 99.9% dependent on SiConnect behaving correctly. Pete
  6. Yes, there are just a few usually more advanced, add-on aircraft which need this. They handle everything themselves from a level hgher that that at which FSUIPC works. Pete
  7. WideFs doesn't have anything to do with folders. it doesn't use shared folders. It just links FSUIPC's WideServer to WideClient on your other PC, using TCP or UDP protocols. SimConnect does the same over a network. Pete
  8. Some Issues of The Axis Assignment

    Ah, you are looking at the Calibration pages. If you assign in P3D, you can calibrate in FSUIPC. But if you want FSUIPC to handle the device you MUST assign the axes in FSUIPC! Please do refer to the user guide. P3D does some automatic assignment, but often gets it wrong. FSUIPC does NOT automatic assignment. It lets you use your devices as you see fit. It really is importnat to read the relevant sectionso of the User Guide. Pictures are provided too! Pete
  9. Some Issues of The Axis Assignment

    There's no "ACE" device seen by FSUIPC because there appear to be not entries for it, either in the Registery, or in the list known to the Windows Joystick interface. That is unless it is this one: Product= Plasma-MM2 78 Manufacturer= Beta Innovations Wouldn't an ACE device feature "ACE" somewhere its identity? If it is that device, it appears to have these connection: Details: Btns=64, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R65535,U65535,V65535,X65535,Y65535,Z65535 i.e 64 buttons and 6 16-bit high resolution axes. I note from the Joyscan file that there are two devices with that identity, but one doesn't respond to Joystick interface reads, nor does the interface give valid informastion, like that above, for it. If that isn't the ACE, but another one which you have working (I can't tell if you have any assignments since you didn't provide your INI file), then I'm afraid the ACE is simply not a device known to any interface FSUIPC understands. Pete
  10. What SimConnect applications have you tried? Does it not work for both local and remote Simconnect clients? DLLs are loaded via DLL.XML and EXE's are loaded by EXE.XML. There might be such filles in both the Appdata\Roaming P3D folder, or in the ProgramData P3D folder, or in both. To stop them loading you just neen to rename or delete those files (but if you delete them you may need to reinstall applications). ---------------------------------------------------------------- That SimConnect isn't standard. Belowis a more 'normal' one, though it is possible for some applications to use different ports. Not that the port isn't required for the 'local' support. My P3D system has IP Address 192.168.0.170, and that is only needed for the 'global' entry, as you can see. Pete <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> <Address></Address> <MaxClients>64</MaxClients> <Port></Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> <SimConnect.Comm> <Disabled>True</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>192.168.0.170</Address> <MaxClients>64</MaxClients> <Port>500</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> </SimBase.Document>
  11. Connecting PLC with FSUIPC

    What drivers come for the PLCs? If they emulate normal Windows Joysticks, with up to 32-buttons per device and 8 axes, then they would be easily supported by flight sims and FSUIPC. Alternatively they might be able to use some other standard USB connections in which case some programming, possibly via a Lua plug-in for fSUIPC would be needed. If they are just plain bits of hardware then you would have to start by programming proper drivers, designing the PC interface, and finally writing a program to drive FSUIPC or a flight sim directly. That might not be good if the devices come with nothing. I'm not aware of any here, apart from a similar question some time ago which basically got the same sort of answer. You'd be better off in a cockpit builders forum such as those on http://www.mycockpit.org Pete
  12. Misssing MakeRwys_Scenery.cfg

    No, you are not reading properly. Here are the relevant sections. I've highlit in RED the part relevant to your misunderstanding: INSTRUCTIONS For: FS2000, FS2002, FS2004 Place the EXE into your main FS folder where the SCENERY.CFG file is located. ... For: FSX, FSX-SE, Prepar3D v1 to Prepar3D v4 inclusive Place the EXE into the relevant main FS folder. ...
  13. 5.123 not installing

    Good. I was getting a bit worried as after tomorrow I'm off on holiday for two weeks, and needed to get this release out and working well beforehand because, knowing L-M, they'll release the next P3D4 update whilst i'm away. ;-) Pete
  14. 5.123 not installing

    There seems to be quite a few types of P3D crash which don't provoke any error message, it just disappears as you'd expect it to do. Note for instance that the P3D windows disappear quite a few seconds before it is all actually closed, so if you, say, shutdown the PC too quickly afterwards that might force it to close, which is the same as a crash. The installation process hasn't changed. but do try 5.123b which is a fixed version of 5.123 and replaced it recently. Pete
  15. Misssing MakeRwys_Scenery.cfg

    Yes. The MakeRunways instructions also tell you this! Pete
×