Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. First off: UpdatedByVersion=4530 Your FSUIPC4 is very old. I cannot support anything older than 4.70, and the current version is 4.758 (installer) and there's a 4.761 (interim update).in the Download Links subforum. Similarly: The oldest supported version of WideClient is 6.86, and there's a 6.92 in the Download Links subforum. Your connection problem appears to be simply that you have two PCs in different workgroups and are expecting Broadcasting to work across them, which won't. You can either change the name of one of them, or add parameters to the client INI file instead so that it knows where to find the Server. All this is actually explained in the WideFS User Guide, in the part about configuring your network. There's even an emboldened red banner imploring you to read it, and there really isn't all that much to read, honest!. Regards Pete
  2. You've done that, and you removed the filtering. Any change to the problem at all? Well the other modules which are also alaways running as well as FSUIPC4 are the PMDG ones: PMDG\DLLs\PMDGOptions.dll PMDG\DLLs\PMDGEvents.dll PMDG\DLLs\PMDG_HUD_interface.dll VistaMare\ViMaCoreX.dll fsInsider.dll Of those I also have PMDG_HUD_interface.dll and ViMaCoreX.dll running, but oddly not the other two PMDG modules despite having the 737NGX installed. Just to see if there's some interaction, could you please try this: 1. Rename that DLL.XML to something different, like DLL.MYXML 2. Run the FSUIPC4 installer so it makes a fresh DL.XML file with only FSUIPC4 loading. 3. Test again. Let me know if that helps. If not, restore your DLL.XML and I'll have to look into what sort of other tests we can do. Regards Pete
  3. No, sorry. All that can be done in a much more sensible and flexible way by using Profiles. Axis and button assignments, calibrations, and so on -- everything you are likely to want differently for different aircraft types -- can be accommodated in one INI and one FSX session, automatically changing over to suit the aircraft you load. That's without reloading FS to change types, and without all the compications of renaming files and multiple settings in separate INI files. This is why I did not implemet the multiple INI facility you mention. In fact it is completely redundant in FSUIPC3 as well because that supports the same Profile facilities. Regards Pete
  4. Try just uninstalling the device. You'll probably need to go to the device manager for that. Control Panel - System - Device Manager. finding the device in the list might not be so easy though. Regards Pete
  5. There's always up to date versions here, in the Download Links subforum -- as well as lots of other useful things. The main Download page supported by Enrico Schiratti has links pointing to the same files for FSUIPC and WideFS, but Enrico doesn't update the text on the page very often -- only on major releases with new documentation. I don't have access to his site I'm afriad. So, although the link there says 4.70b or 4.70c, it actually does download the installer for 4.758 -- with 4.70 documentation. I'll have to get him to update the text with the next major release -- probably 4.80 in February. I need to replace everything in February because the signature on everything expires on February 12th 2012. I now have an updated signature lasting till 2015. Regards Pete
  6. Yes, that is what it should do, and it at least shows that your MCP is working, that the displays do actually light. That was the reason to check that, nothing more. Hmm. Interesting. So you supplied the serial number to them when you purchased the driver? I've marked in red those parts different to mine. You have an MCP Pro with Version 2.0 of the firmware. mine is at 1.1. Seems they've changed a lot -- as well as the missing serial number, look at the Output and Feature values. It seems they've changed the way the displays are handled, from using "SetFeature" for everything to normal data Output methods. I would guess that SetFeature is now only used to set the brightness., with all data for the displays going via the normal data output routes. You certainly need to talk to FSL about this. I think it is likely that their driver, if it interfaces directly to the MCP Pro rather than going via GFDev.DLL, is working on the earlier method for the displays. Did you try with an updated GFDev.DLL placed in with the FSL driver, just in case? If they are using GFDev then I should have thought that would solve the problem. However, if FSL are really reading the serial number then they must be bypassing GFDev, in which can they'd need to change their driver for the Version 2 firmware. Regards Pete
  7. Yes, there is a 'sync' facility on the 4 throttles calibration page and it is documented in the User Guide. This allows you to calibrate so that both throttles provide the same input when they are lined up. It is done by calibrating a number of "sync points" in order to get around differences in the axis travel. Alternatively there is a Hot Key setting you can assign which simply makes all throttles follow throttle 1 until you toggle it off again. This is also documented in the user guide. It would be well worth your while browsing through the User Guide and seeing what FSUIPC offers. You might find things out more quickly than posting here for each question. ;-) Pete
  8. Yes: this is nothing whatsoever to do with FSUIPC, but it is the well-known problem of the Windows 7 version of UIAUTOMATIONCORE.DLL not being compatible with FSX. You'll find solutions over on AVSIM's FSX Forum where this has been a recurrent theme. For example: http://forum.avsim.net/topic/360394-fsx-ctd/page__p__2233535__hl__uiautomationcoredll__fromsearch__1#entry2233535 and http://forum.avsim.net/topic/334306-fsx-fatal-error/page__hl__uiautomationcoredll__fromsearch__1 Pete
  9. Sorry, I don't understand what you mean? You want a blank screen? I would have thought that would have been rather worrying. FSUIPC really can't do anything about video effects. The view changes you are talking about merely use regular FS controls. Regards Pete
  10. Sorry, no. I do not work that way. So far you've supplied zero info on the problem in any case, seeming instead to totally misunderstand what you are seeing. The information will be in the logs. Both of your assumptions about Prepar3D are totally wrong and rather wild. The information needed is in the Install log. That is precisely why it is produced and your delay in showing such information is rather strange. Why would I need to see screen prints? All I need in the first instance is the Log. That's the whole point of producing one! I also need you to confirm the VERSION number, not just saying "latest". you've not even done that yet! If you are not using 4.758 you need to update first. Perhaps you can start soon, then? ;-) Regards Pete
  11. Please don't purchase FSUIPC unless you actually want to use any of its facilities. Browse through the user guide (installed in your FS Modules\FSUIPC Documents folder) first, to see if it is worth your money. Registering it won't necessarily fix any problem you've got -- we don't know why your system is crashing after 70 minutes in any case. Certainly an unregistered FSUIPC is doing far less than a registered version would be. If you want, instead, to determine the reason for the crash there are other steps to take, as i tried to explain last time. One other possibility, for instance, is a corrupted weather download -- if you are using FS's real weather facilities. One of the few things FSUIPC is doing when unregistered is getting weather data from FS in case any application program wants to read it. Unless some add-on you are using actually uses FSUIPC for anything, it is doing virtually nothing else, just sitting in a loop reading weather once or twice per second. Regards Pete
  12. No version of FSX, ESP or Prepar3D creates a DLL.XML file -- unless you install the SDK. That doesn't matter. If one isn't there, FSUIPC's installer creates one with only it listed for loading. Again, no version of FSX, ESP or Prepar3D creates a Modules folder. That is also done by the FSUIPC installer. Versions of FS since FSX have not used a Modules folder, but in FS9 and before that was how added modules got loaded. FSUIPC creates the folder to maintain the sort of compatibility with user's expectations it was designed for. Saying your version of FSUIPC4's installer is "the latest" is actually rather meaningless to me I'm afraid. Folks have said that when they were actualy using a pretty old version -- just the "latest" they'd seen. Please always quote version numbers. If you are using the 4.758 installer, show me the log or at least look at it and see what the problem is. Regards Pete
  13. I cannot support other folk's software I'm afraid. However, maybe it is simply that the GFDev.DLL interface is out of date. You can find the latest one in the Download Links subforum here. Possibly. I don't know what gets installed at lower levels for GoFlight. The GFDev.DLL is a user-level interface. I suspect the buttons and knobs work okay because they are normal joystick-type inputs and the standard Windows drivers cope, but, of course, displays are rather specific. There may well be a lower-level driver which operates the disaplys and which you are missing. Tell me, when you unplug the MCP USB and plug it in again, do the displays light up for a short time? If not you probably have a hardware problem. There's a program of mine called "HidScanner" available, also in the Download Links subforum, probably in the thread on Lua plugins. Get that and run it. It should show all HID devices, including GoFlight, and it doesn't depend on GFDev.DLL. It'll produce (and display) a log file. The GF MCP Pro lists like this: Device at "\\?\hid#vid_09f3&pid_0064#6&e096aa2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=09F3, Product=0064 (Version 1.1) Manufacturer= GoFlight Product= MCP PRO Serial Number= 0004 41 Usage Page: 14 Input Report Byte Length: 8 Output Report Byte Length: 0 Feature Report Byte Length: 8 Number of Link Collection Nodes: 15 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 1 Number of Feature Value Caps: 9 Number of Feature Data Indices: 41 Buttons range 1 -> 32 at indices 1 -> 32 Value Dial at index 0, range -8 -> 7, using 4 bits ************************************************************************** I think the displays are driven by "SetFeature" commands at the USB driving level, so the entries there relevant to the displays are only: Number of Feature Button Caps: 1 Number of Feature Value Caps: 9 Number of Feature Data Indices: 41 Regards Pete
  14. More information is needed. It sounds like you are using an outdated version of the FSUIPC4 installer. The current version is 4.758. If the Installer ran with no errors, where is the Install log? What did it actually do? It displays a complete running log sdaying exactly what it is doing, every step. Even if you cannot find the log file itself, you can read it on screen. There's a scroll bar and even a Save As menu option. Regards Pete
  15. Ah, thanks. Another TLA. The world's filling up with them! ;-) Regards Pete
  16. It certainly sounds like something you have got added into fSX is using FSUIPC wrongly. Either that or there is something very wrong with your FSX installation. Please, I can't help without details. Find the Windows error log entry for the crash. Right clcik on "My Computer" and select Manage, then look in the Event viewer -- Windows Logs - Application, find FSX and the details. It should confirm FSUIPC4.DLL and provde a crash code and a module offset. FSUIPC always saves the options when you change them, so it never loses them. Unfortunately FS isn't as well behaved. You have Windows set to hide filenames from you and instead simply tell you they are text files or configuration files. A log file is a text file, with the filename FSUIPC4.LOG. The configuration file s FSUIPC4.INI. The log file sohws a perfectly normal run, no crash. It terminated correctly. However, the session the log relates to only lasted 21 seconds. It also shows that you haven't registered it, so I'm now wondering why it is installed. What programs or add-ons are you using which requires it? An unregistered FSUIPC is really doing nothing much at all unless it is there to support some application. Naturally, the log which would be more interesting and useful is the one which is available AFTER the session where you got a crash. Why are you now SHOUTING? That isn't warranted. An FS session which crashes after 70 minutes is most likely cras hing because of things like memory failure, overheating, or, possibly, corruptin in memory due to bad or corrupted scenery elements. Maybe your crash is more related to the area you arrived into at that time. Crashes caused by memory failure or corruption are notoriously difficult to locate, and can cause a crash in almost any part of the FSX program, including FSUIPC which is merely operating as another FSX module. Without more details, as I mention, the only way to narrow down your crash problems is by a process of elimination. As you haven't registered FSUIPC you don't have access to its Autosave facility which would have enabled a repeat of the few minutes leading up to the cradh, to determine whether it is locality-related or time-related. Maybe you can try to re-create that point in any case? Regards Pete
  17. FSUIPC provides mouse look too -- it's an option in the Miscellaneous settings. Where are you looking for the Throttle calibration? Which page in the tab? If you are assigning to separate throttles for each engine that will be on about page 3. The single throttle calibration on the first page, with aileron, elevator and rudder, is the single generic throttle for al engines ("THROTTLE SET" or "AXIS THROTTLE SET"). Regards Pete
  18. Okay. Nothing there truly odd, but a couple of questions and suggestions. First, I see all your Button assignments are to keypresses, every single one. Are they all to do things which FS cannot do -- i.e. all aimed at some add-on? If not, if you are using them for FS controls, it is a very very inefficient way of doing thnigs. You'd be far better off assigning to the relevant FS control instead, for every one. Second, you have two axis assignments which operate on 'ranges' -- i.e. the right-hand side of the axis assignments -- in one case instead of any true axis input: This one: 2=0U,256 3=0U,B,-16384,16383,65786,0 appears to set the complete possible range to sending FS control "SPOILERS SET" (65786). So why not simply assign to that control instead? You used Direct to FSUIPC Calibration for other axes, why not to Spoilers too? This one 7=2Z,256,D,4,0,0,0 8=2Z,BR,-16384,-14173,65602,0 Looks okay. Instead of mapping the throttle ot the 4 separate throttles so you can have a reversed zone you've used the right-hand zone settings for "THROTTLE_DECR". An interesting solution, I suppose, to those add-ons which don't like the normal way FSUIPC accomplidhes this? In the calibration section: Aileron=-16223,-481,416,15264/8 Elevator=-15322,-224,256,16064/8 Rudder=-16384,-260,-260,16256/8 Throttle=-8192,16383 LeftBrake=-16384,16256/24 RightBrake=-16383,16256/24 you have 5 of the 6 axes set with "Filtering" enabled. That worries me. Really filtering is a last resort for very dirty or badly behaved controls or extremely poor power -- it was originaly added to help a chap with wobbly mains power in the Malaysian jungle! I'm paricularly concerned that the filtering relies on extra timers and Windows messages which might be getting blocked by other add-ons, so please try without. You can do this most easily by changing the above to: Aileron=-16223,-481,416,15264 Elevator=-15322,-224,256,16064 Rudder=-16384,-260,-260,16256 Throttle=-8192,16383 LeftBrake=-16384,16256/16 RightBrake=-16383,16256/16 Please also can you tell me what other non-aircraft add-ons are running inside FSX? Maybe the easiest way is to show me the DLL.XML file, from the same folder as your FSX.CFG file. That does sound like some sort of hangup on a joystick driver during the scanning. Can you check the Windows game controllers (or, in Vista/Win7 the "devices and printers" applet) to see if it lists anything you don't actually have connected? Regards Pete
  19. You supplied the Install log, but isn't there a Run-Time log (FSUIPC4.LOG)? I'd need to see that. If FSX is loading to the 100% mark it sounds like a corrupted weather file (WX file in your Documents Flight Simulator X Files folder), or maybe the wxstationlist.bin file in the same folder as your FSX.CFG (i.e. in C:\Users\Mike\AppData\Roaming\Microsoft\FSX). Try deleting that and rpelacing it with the default one in the FSX Weather folder. Otherwise I need to see the FSUIPC4 log please. Incidentally, the Install log shows this: which means you are using the original buggy version of FSX. I would strongly advise you to download and install the SP1 and SP2 updates. There were lots of problems in the original release which are fixed by these updates. Regards Pete
  20. I don't know what a UAV is, but if you assign in FSUIPC to can add delays by editing the assignmnet lines in the INI file. See the Axis Assignments section of the FSUIPC Advanced User's guide. Regards Pete
  21. I don't know VAFS, but if it uses FSUIPC for its interface to FS it should work fine under WideFS too. If it needs to access FS's folders for data you may need to make those folders shareable over the Network. [LATER] Just Googled VAFS and it seems to only need FSUIPC and, of course, your Network connection. So you should be okay under WideFS too. Regards Pete
  22. The VRI MCP I have has the transponder code in its radio section, and can be set as easily as any of the radios (COM,NAV,ADF). It's selected by the button labelled "TRN". The VRInsight driver operates the default FS transponder setting well, and that will also be the one read by FSInn, so you should be okay. What is usually the harder problem is setting the transponder mode, because FS doesn't really simulate this. How you program that wil depend on what facilities FSInn offers for its assignment. Regards Pete
  23. What panel functions does FSInn need? I thought it operated using on-screen buttons and selections via mouse clicks? It's a little complex with VRI devices if you want to use the VRI driver for most things but FSUIPC to reprogram some things. Instructions are provided however, and you'll find Andy over in the VRI support forum very helpful indeed. That's the place to ask about most things VRI. As for programming keystrokes, whilst this is possible it is generally better to use FS controls where possible, as it is for the default FS autopilot for example. None. There's only one version, not separate 'free' and 'pay' versions. It primarily acts as an interface into FS for application programs. You pay for a Key to unlock the user facilities which are otherwise inaccessible and inoperable. User facilities include assignments, VRI support, Goflight support, calibrations and many others. Best way to find out it to install it in any case and browse through the User Guide which tells you these things. Regards Pete
  24. This is almost always a symptom resulting from a joystick or joystick driver misbehaving and sending continuous signals. Do you get any display of joystick number ot button number or axis at all? Is it possible you have some joystick driver installed for a joystick you no longer have connected? The calibration tab only beeps when attempts are made to enter values in something other than ascending order, left to right. Can you please do two things: 1. Show me your FSUIPC4.INI file, from the FSX Modules folder. Best to paste its contents into a message here. 2. Rename that file, to say FSUIPC4.oldini, then run FSX again and see if it works okay then. If so, it will be something corrupted or set incorrectly in the INI file. All that does is re-scan the joystick devices to see if any new ones have connected or old ones disconnected. If doing that changes things it sounds definitely as if one or more of the devices you have connected is playing up. Perhaps you could unplug them all and try one at a time, to see which it is? Well, 4.50 is a couple of years old so there are certainly a lot of new facilities and fixes in that period, but I don't know of anything which can specifically give the symptoms you describe. Regards Pete
  25. Okay. I'm sure it must be something simple as it works for so many folks without any issues whatsoever. But without any information at all I don't see how anyone can help. The reason FSUIPC4 makes log files is to record enough information to resolve any problems or other questions. Without any sight of those it is well nigh impossible. You are the first ever user in the 14 years of FSUIPC who, after asking for help, couldn't show this information. Such a shame. Not sure of the relevance of this. If it's in relation to cut and paste or copy and paste, I normally use the normal right-click popup menus. Easier than remembering keystrokes and fumbling about with multiple key presses. In fact, including the double click on the log (text) files themselves in order to open them in an editor, it's pretty much all mouse work. Regards 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.