• FSUIPC v4.947 October 10th 2015 release. Works with Prepar3d V3 1. Install, at the end select 'not now' for registration 2. Copy Contents of /crack folder in the. • Add-on navigation tool for Flight Simulator including flight planner, moving map, GPS, AI traffic with TCAS and procedure generator. Displays airways, 12 airspaces. • Serials, numbers and keys for Fsuipc 4.9.

Facilities provided to the Registered User of FSUIPC include: Joystick control facilities: Facilities for joystick calibration – specifically, more accurate setting of dead zones and centres. FLIGHTCONTROLREPLAY PROFESSIONAL EDITION FSX P3D. SIMELITE SOLUTIONS - TIME ZONE FIXER FSX P3D. I have FSX / Accelerator and FSUIPC 4 ( version 4.9.4.9 ).There are updates listed below for those who are interested. With what Im using which ones should I download? FSX - FSUIPC 4.70 + CRACK by Erick Matheus on. Julho 05, 2015 in FSUIPC Tamanho:5.83MB Download. Tamanho:5.83MB Download. Tags # FSUIPC. The screens are black although i have installed the newest version of fsuipc for FSX SE, can you help me? Share this post. Link to post Share on other sites.

The log file snippets I posted were from FSX and just posted to illustrate that I 'use' that function, for lack of a better term:) Paul. Errr, but it does/did. I see you released an update for it. No offense, but I give you a bug report that definitely shows it was caused by the program (and verified by many others on forums) and that's the kind of response?

I have the PFC drivers installed and those devices were seen in FSUIPC when I used the PFC specific setup routine available through the FSX addons menu option. I also believe that the serial connections might have been causing the phantom spiking that your program detected, and was evidenced by the involuntary inputs to the other devices in FSX, specifically in this case helo rudders moving without any input from the HID. The Flight Link rig seems to use standard MS drivers as there's nothing specific from them available in that regard. The serial devices (pedal/throttle box in the PFC rig) are conneted directly to a serial port on the PC. The pedals/collective on the Flight Link rig are connected THROUGH the Flight Link G-Stick housing and that housing is connected via USB to the PC. I am NOT using any external serial/USB converter plugs.

Why did you post about six messages with nothing but 'Hi Peter' in them? You are using the wrong version of FSUIPC -- you need 4.738a. Pete Sorry peter about the posts i know of 1 but not 6 I hit tab by habit and all went mad. OK about 4.738a no I will not be I have redownloaded now and will reinstall to night when I get home.

That said, if they continue to work for FSX but not FSX-SE, that would not be a problem as we will never bbe flying as a group on Steam. We require the access to the Digital Theme Park servers vis the FSX 'Lan' connect option, which is missing in FSX-SE. Again, thanks for the quick work on this in spite of your 'ill' machine and the coming holidays! Paul EDIT: I just had a look at my FSX FSUIPC4 log for this mornings 6-hour flight to Berlin and back from UKBA: It caught several G3D errors!

(GoFlight devices connected via WideFS are okay, still using a 32-bit WideClient and 32-bit GFDev.DLL locally to the client PC). VRInsight original serial port device support. PFC COM serial port devices previously using PFCFSX.DLL. The conversion of this module to the 64-bit version (potentially called PFCCOM64.DLL) will be under way shortly after the public release of FSUIPC5. PFC Hid devices previously using PFCHID.DLL. The conversion of this module to the 64-bit version (potentially called PFCHID64.DLL) will be under way shortly after the public release of FSUIPC5. Other facilities 5.

Do not see any update about it being an 'a' ver. Thank you for your fast reply will post this info on our user forum so other there know. Best of the season to you.

The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch. In the latter case the code in that area has changed and i'm not sure whether the fix would still be needed in any case. Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas! Great news Pete! That is with a couple of reservations for my use.I have seen 'the 'G3D crash' patch' do it's thing several times recently when I was flying around the EU with OrbX Global + Vector + Europe LC + Hybrid mode. Also, I and others in the 91st Bombardment Group use those weather setting options in FSX during the missions that we fly because we can not tolerate 'different wind directions/speeds' betwen users and we can not dictate to our members that they buy a commercial weather engine and then be constantly 'chasing the upgrade path'!

I'm pleased to report that after a day of struggling (Friday) I got my development PC working well enough to do some work. I just dare not switch it off or I think it won't come on again! It is crippled -- it won't run P3D because I had to substitute an older non-DX11 video card. But it was okay for testing with FSX and FSX-SE, FSUIPC Version 4.938 is now available, and works as best as I can make it with FSX-SE. The installer copes with both ways FSX-SE installs (free-standing or alongside FSX Boxed), and all the hooks appear to work except for the full wind-smoothing fiddle (rarely used these days with such good weather programs), and the 'G3D crash' patch.

How can you do that when it is already USB? If you bypass the FlightLink device which is making it look like a joystick what will it look like? What will recognise it? Do you mean Game Port?

I am talking about FSX as that is my primary online simulator. It wasn't clear to me that those comments about wind smoothing and G3D errors were FSX-SE only conditions. As long as the wind smoothing and G3D crash protection still works in FSX I'm happy. The log file snippets I posted were from FSX and just posted to illustrate that I 'use' that function, for lack of a better term:) Paul. Errr, but it does/did. I see you released an update for it.

I've got both PFC fixed wing and Flight Link rotary controllers. These units are fairly old and are still using serial connections in some of their setups.

It is certainly of a low priority. Programs needing such information are now better reading the AS16 (etc) Weather files themselves, which are stored in a known sharable folder. WideFS file transfer: this is probably not used at all these days, so will be discontinued. Other facilities 8.

Errr, but it does/did. I see you released an update for it. Hataraku maou sama ova sub indo w.

Both parts are transmitted to WideClient for display locally, inside the cockpit, on a client PC. I will be pressing L-M hard for a good implementation of this. Control acceleration fix: I’ve really no idea if this is still necessary.

I don't know of any way you can get cross-interference from separate devices, and especially separate devices with separate drivers, UNLESS there's some mlutiple assignments going on, possibly ones you aren't aware of. Pretty much all cases like that have been down to such a mix up. That's why Paul suggested we clear out all assignments from the fsx.cfg file and do a 'virgin' setup within FSUIPC. Again, that is nothing like you seemed to describe earlier. The device is evidently a bona fide USB joystick type device as far as Windows is concerned. Sorry for any confusion.

Feedback on any of the FSUIPC facilities would be useful, but I may not deal with it now for a week or two!;-) Oh, the latest version of MakeRunways, also available, also copes with FSX-SE's possibly different SCENERY.CFG location too. Happy Christmas! This part of your post is confusing me. Are you talking about FSX or FSX-SE?

So, bottom line, there are those of us who use those wind smoothing functions. That said, if they continue to work for FSX but not FSX-SE, that would not be a problem as we will never bbe flying as a group on Steam. We require the access to the Digital Theme Park servers vis the FSX 'Lan' connect option, which is missing in FSX-SE. Again, thanks for the quick work on this in spite of your 'ill' machine and the coming holidays!

Both use the same download file and install process so I suggest getting the freeware version first, install it and have 'play' around with it. The differences in functionality is easy to see - all of the payware functions are there but 'greyed' out.

Unlike standard 'joystick' devices, which have to abide by a particular protocol to be recognised as such, serial port devices all do their own thing at the whim of the hardware or firmware designer. There's no doubt that your serial devices will work with the correct driver, made specifically to understand what they send to the PC. I don't understand how the devices were acquired without their driving software, but I would have thought the first step would have been to search for such drivers if you have a clear identifier and make for the devices. What i don't understand, from what's been said here so far, is how he got anything from the serial devices recognised at all without some software installed to read them. Looking back, he said.

But, since Windows assigns these IDs sequentially according to the number connected, I cannot imagine that number being exceeded. I've never known it happen. All this having been said, I'm simply looking for a soultion whereby all devices will be seen and able to be programmed through FSUIPC. Do you believe that converting the db15 connectors to USB on the Flight Link will help? How can you do that when it is already USB?

OK about 4.738a no I will not be I have redownloaded now and will reinstall to night when I get home. Do not see any update about it being an 'a' ver. Thank you for your fast reply will post this info on our user forum so other there know. Best of the season to you.

What i don't understand, from what's been said here so far, is how he got anything from the serial devices recognised at all without some software installed to read them. Looking back, he said. I'm not aware of any serial driver interface to FSX, as everything nowadays uses USB2 or 3. There's never been any possiiblity of a 'generic' serial port interface in any case, as there has never been a standard for such devices to follow. The same could apply to USB devices too. There are certain laid-down standards for USB devices to adhere to if they are to be recognised without their own specialised drivers. These classify USB devices into things like storage devices (USB sticks and hard disks) and HIDs (Human Interface Devices) of which Keyboards, Mice and Joysticks are standard, but others may do their own thing (like GoFlight devices other than their throttle quadrants).

The products themselves are downloaded from: Make sure simmarket.com is allowed through your ISP and any installed spam filter you have. If you first download FSUIPC and install it (you can do this without registering it) you'll find in your FS modules folder the user guide which describes the advantages of buying a full registration yourself and describes the purchase and registration process. FSUIPC3 for FS9 today is EUR 23.80 including VAT or EUR 20 outside the zone that applies VAT. FSUIPC4 for FSX is just about EUR 4 more.

No offense, but I give you a bug report that definitely shows it was caused by the program (and verified by many others on forums) and that's the kind of response? I'm afraid that FSUIPC is now so complex, and old (FSUIPC4, the 4th incarnation) has now been continuously developed now for 9 years -- and every update with no extra charge, mind -- that an old man like myself (well over 71 now), who should have stopped years ago, doesn't remember everything all the time and sometimes makes mistakes. But I do try and make up for it.

Thanks, Alan. Pivot ben 10 ultimate alien pack download.

I am NOT using any external serial/USB converter plugs. Again, that is nothing like you seemed to describe earlier. The device is evidently a bona fide USB joystick type device as far as Windows is concerned.

Meanwhile, displays will be routed to the default “message window”, as used for general messages and which by default in a bar along the top (which can be resized, moved and undocked). Mouse Macros: I have asked L-M for facilities to allow this to be implemented, hopefully in a much nice fashion than the 32-bit hacks which are really quite crude in their operation. However, to be honest, I’m afraid this is one of the things I’ve got less confidence in L-M coming up with anything. SimConnect Text & Menu Interception: Now, as a cockpit user, this is one of the main things I’m interested in.

He's building up what will be a fairly complex airliner-style flight deck ( not there yet), and some of our time was spent moving from the pretty 'Windows 7 for Dummies' interface over to an XP-style interface, where he could access the.ini, fsx.cfg and the standard.xml files, etc. The serial/USB issues only cropped up after we successfully recognised the USB X & Y axes and then ploughed into a serial rudder and throttle. There's a second controller setup (for heli's) that we looked at, but it has a 'converter' on it, and, although lots of 'in-out' activity - it wouldn't work either, so we abandoned the endeavour altogether, and Alan is now waiting for his new GoFlight unit to arrive. We did, however cover the processes of profile creation, axes input and calibration, and buttons/swithes inputs, so he should be all set for when the new arrives. I was pretty sure that serial interface was not supported, Pete, but whether FSX or FSUIPC - I wasn't sure - only remembering something about serial not working some eight years ago, but now being too old to go back that far.:) Thanks, pj. Hi Pete: Alan has one USB device hooked to X & Y yoke axes, but as we went along it became plain that all other connectivity was either direct serial, or USB through one of the mickey-mouse serial-usb converters (which don't work).