Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. "AP Master" is the FS control assigned to "Z" by default. Regards Pete
  2. In that case FSUIPC is really not involved, is it? Yes I know. I think you need GoFlight support for this. Yes, provided that other software deals with it through its FSUIPC interface. But I don't know of any GoFlight software which does this. Surely the MCP would connect direct to the pmMCP and use an INI file paramter to tell the pmMCP program to use that hardware? At least this is how it works with the PFC MCP, and the CP Flight MCP. In that case I can only assume you were using some Goflight program which has an interface to the pmMCP via FSUIPC offsets. I'm pretty sure GFConfig doesn't do that, but maybe there are other GF programs or modules which do. In that case it would seem that are some files you are missing or some CFG ot INI parameters wrong. You really need to check the GoFlight documentation on how to set it up to work with PM. Isn't there a Support forum for GF? The PM forums over on MyCockpit might be good place to ask, too? Regards Pete
  3. Why not download and install, first, then purchase? Seems odd to do it that way round. There's no "module" pull down box in FSX. SimConnect adds a menu entry named "Add-Ons". It would be the right-most entry in the normal FS menu, the one along the top of the screen when you press ALT. That's fine. Nothing wrong there. Maybe you are looking for the wrong thing? Pete
  4. What aircraft is this with? If you are using an add-on with its own Autopilot then neither the Autopilot Off control nor Z will work. You need to use whatever it is that the add-on aircraft needs to see. Regards Pete
  5. If you want it loading automatically when you run WideClient, yes. It's your option. If you only want it to run when FS is ready you should use "RunReady" not "Run". Er, yes, well, okay -- it didn't see the broadcast from the FS PC. But you only ran it for a few seconds. Are you sure FS was running and ready to fly then? You should not be so impatient. See it it connects later -- WideServer won't even be trying in any case till you are completely ready to fly. This log shows WideServer not even being started till 38 minutes after you ran WideClient! If you don't run them at the same time, they cannot connect! Nothing can bypass firewalls. You have to either turn them off or, more safely, make the exceptions at both ends. Regards Pete
  6. There's nothing wrong there. Everything is fine, though you certainly omitted to mention that you were running WideFS too!! Perhaps there's something on your Network responsible for your 5 second interval pausing? When you tried with FSUIPC unregistered, was WideFS unregistered too? They are independent in this regard. If you don't enable WideServer, do you still get the problem? In your network settings, have you set fixed specified IP addresses, or are you allowing Windows to seek IP connections every few seconds? There's no 5-second interval action in FSUIPC or WideServer, but there may be elsewhere, possibly enabled by whatever you are selecting. Regards Pete
  7. Obviously you have something assigned to the panning action from one of the rudder or throttle quadrant levers or buttons. Why don't you check? Regards Pete
  8. And what, then, do the Log files show now? I cannot advise without this information. If there is a problem it will be logged. By not supplying information you are simply delaying any solution. I cannot actually see you computer screens from here, and I cannot guess accurately, if at all, what is happening. Of course -- if WideFS is not able to connect then how can Squawkbox? Regards Pete
  9. Okay, that simply shows that the client didn't see the Server. Are you sure it's "WORKGROUPS" and not "WORKGROUP"? I think the default name like that was in the singular. And also now remove the ServerIPAddr, ServerName and Protocol parameters, if you put them all in, from the wideclient.INI file. Yes, of course. They must be different else they wouldn't be differentiated. Yes. That's what WideClient is. When linked to WideServer in any version of FS, it presents the FS98-compatible application interface which has been maintained and extended now for 12 years, without the need for FS98 to be installed on that PC. ;-) Regards Pete
  10. They are both WideClient logs. The WideServer log is the other half of the story -- it'll be in the same folder as FSUIPC, i.e. the FS Modules folder. Oddly the two logs you showed are from two different configurations in WideClient.INI, so it looks like you've been trying something. Care to explain? This, from the first, indicates the two PCs are either on different WorkGroups, as I suggested, or simply not talking to each other at all. whilst the second one, from a couple of hours later seems to show that you've added the "ServerIPAddr" parameter with 192.168.1.2 as the server IP, but windows is finding this to be an invalid IP address, not referring to any PC it can see. Just change the Workgroup in one or both so they are the same. i use "PETES" as my workgroup name. You can change the workgroup name in the same place as you change the computer name -- the Properties of "My computer" (right click and select properties). Pete
  11. Providing each joystick connection is recognised by Windows as such, and you don't exceed the FSUIPC limit of 16 joystick devices in total (with Windows assigned ID's 0 to 15), each with up to 32 buttons, then, yes, just add another. Again, provided whatever you connect by way of a joystick axis is recognised by Windows as such, and is one of the basic 6 axes (XYZRUV) and not the two extra slider axes added by DirectX, then they will be seen and assignable in FSUIPC. If you were using FSX and FSUIPC4 all 8 axes would be available. Regards Pete
  12. Ideally you'd think matching the render frame rate would be smoothest. However, you don't know when, within that time, the SIM engine is computing the next values, nor, in fact, when those values have their effect on the screen. Suppose you are spot on, sending values exactly at the frame rate, but meanwhile the SIM engine has just passed its latest computed values to the rendering engine? Your new values now take a whole frame to have any effect and by that time they should probably have been different. The only way around that is to try and get more updates done within each frame, so you have a better chance of being "right" on the mark. Naturally you have to have a limit, but that will be dependent upon the performance of FS on this specific PC. Regards Pete
  13. No. WideFS doesn't "locate Squawkbox". You shouldn't need to edit anything in any INI file in order to get WideClient connecting. The usual reasons for it not connecting automatically are: 1. The two computers being on different WorkGroups. This is happening more these days because Vista and Win7 have different default WorkGroup names to XP. You should put all your PCs into the same workgroup, but otherwise you can edit the WideClient.INI as described in the user guide, to allow use on more than one workgroup. 2. There's a firewall blocking the connectoin at one end or the other. 3. You have other problems with your Network. I may be able to advise a little more if you find the WideServer and WideClient log files and pasted them here. These logs are produced for a reason -- to show you and I what is going on. I can't advise on Squawkbox. That's a different package which I don't know. Regards Pete Clive
  14. I assume you do this all in one Process call per cycle, so only causing one process switch? If not you certainly should. Do the writes and reads at the same time. It is extremely difficult to escape from that entirely, even with the change going on as fast as possible from inside FS. I know, I've tried to do this. FSX is worse than FS9 because I'm going through the SimConnect interface. FS9 is better because many of the things have direct access into SIM1.DLL's variables. Is your program an in-process DLL or GAUge file, or an external EXE? Internal actions can of course be repeated at a much higher frequency, which does help. With FS9 the best approach is really do do it as fast as possible without actually causing any noticeable deterioration in frame rates etc. For FSX, as fast as possible helps but the asynchronous nature of the SimConnect server-client approach will never give ultimate satisfaction I'm afraid. All you can do, as with most things FSX-wise, is recommend the fastest hardware the user can afford! You might want to consider using SimConnect directly for your FSX version as in this case FSUIPC is really only another layer -- though admittedly, SimConnect is a lot faster for internal clients like FSUIPC. Regards Pete
  15. Show me what you've done, or speciofically what you don't understand in the instructions. I can't explain here better than in the documentation -- if I could it would already be like that in the documentation, don't you see? Why would I prefer to type it differently over and over in a Forum than once and for all in the documentation? If English isn't your natural language, perhaps you could get someone to help? Regards Pete
  16. In FSX assign it to the Pan View axis control in axis assignments. If FS9 the best you can do is shown in the example in the documentation. Why use F2? If you want a reverse zone follow the instructions in the documentation. Regards Pete
  17. What software is supposed to be controlling the GF-MCP? Have you programmed it all in FSUIPC, otr are you using the GF software? If the latter, then FSUIPC doesn't come into it. Sounds like whatever software you use to link the pmMCP program to the GF MCP hardware either isn't running or isn't set up correctly. But nothing you've said indicates that FSUIPC has anything whatsoever to do with it. What does your MCP Pro hardware use to talk to pm's MCP software? And if pm's MCP is supposed to link to the GF MCP shouldn't they both be on the same PC? Regards Pete
  18. It doesn't matter what it is provided it matches exactly your registration details. It's the address or zip code or whatever you used when purchasing the registration. If your installation is already registered and you want to check it, you select "check". If it isn't, you need to enter your registration details. Your registration details are the ones you used originally and never change. They are those recorded for you when you purchased the key. If all you did was re-install Windows, and you had not touched the FS installation, so the FSUIPC files were all still intact in modules, then, yes, you could have got the registration re-instated by using "check". Did that apply to you? Most folks, when re-installing Windows also re-install everything else. not you? It doesn't do any harm in any case. It would tell you one way or the other. Regards Pete
  19. Of course it could be that your joystick, or whatever it is you use for panning, has actually broken. If there's been no software change whatsoever then a hardware change is obviously the only possibility left. Yes, as I suggested. If nothing is assigned to it, it cannot happen. So you must have missed something. If it is your Hat switch, as you say in the title, then check its assignments both in FSUIPC and FS. Otherwise, what do you normally use for panning? Only the keyboard? If not, then what? If it's buttons or a hat, check those assignments. If you think it might be something you've set in FSUIPC please go to the FSUIPC options, enable Event and Axis logging in the logging tab, see the problem occur, close FS, show me the FSUIPC.LOG file and the FSUIPC.INI file, both from your FS Modules folder. Regards Pete
  20. Versions 3.983 and 4.603 are now available and fix the Windows saving issues. Regards Pete
  21. Seems that FSX must have crashed soon after loading then. But that certainly wasn't so when the FSUIP4 log was made, ass that ends after at least 5 minutes of operation with a normal closure: Maybe. Glad everything is okay now. Pete
  22. In that case it is probably a Simconnect problem. The Log file should show what is happening. When there is a difference in behaviour with and without registration, then the registration is always in question. I don't sell FSUIPC, SimMarket does. I don't have a database. And I was not accusing you of not having a valid license, but only suggesting the possibility of the license information installed on your PC as not looking correct. For example, if your system date is for some reason wrong, and earlier than your registration purchase, it would make the registration look invalid. Regards Pete
  23. That's very odd. Can you get any more details? Something is evidently conflicting. Also please try swapping the DLL with the latest increment from the Updates announcement above. Regards Pete
  24. Ah, good. I respond to each message as I come to it and failed to note there were more below the first one I'd not seen. Thanks! Pete
  25. Please refer to the section "Multiple INI files" in the FSUIPC4 Advanced Users Guide, where you'll find this: If you give a name beginning with “FSX”, such as FSX_for_Choppers.EXE then FSUIPC4 uses the appended part for its files, thus: FSUIPC4_for_Choppers.INI (also for .LOG, and even .KEY—so remember to duplicate your KEY file and rename it accordingly or you will find yourself unregistered). Pete
×
×
  • 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.