Pete Dowson

Okay. Thanks. Those file parts are useful. I'll check -- but it will be tomorrow or more likely Monday now. Pete

Strange. Have you tried with the MSFS update? Pete

Does this apply to "real traffic" as well as AI? Does LittleNavMap show the routing? I know it also reads the traffic data via SimConnect, though it uses the 32-bit FSX SimConnect DLL. I suspect it's yet another limitation of the currently implemented SimConnect interface. If the information was arriving it would be available, but it's possible that requesting those things was causing errors in an earlier version of the MSFS SimConnect interface and so were (temporarily) suppressed in FSUIPC. If so I expect John can un-suppress them to see if they now work. Pete

FSUIPC only directly supports Joystick type HID device -- that's one with the Capabilities showing UsagePage = 1 and Usage 4. If your device only has switches, buttons, POV hats and analogue axes then it would be more universally accepted classified as a joystick, not just by FSUIPC. Currently FSUIPC directly supports joysticks with up to 32 buttons, 4 POVs and 8 axes. If the device has displays or indicators then those aren't supported directly in FSUIPC itself. FSUIPC does provide more generalised HID support for plug-ins written in Lua, but no direct support without programming of some sort. Pete

You translated his name into Spanish! 😉 Roman's Lua appears to be a semi-automatic way of discovering what should be in the DontLogThese parameter, so would actually still be useful after you implement the changes in FSUIPC too.

😉 Glad to see you back, though I think it'll be quite a while before MSFS is suitable for my cockpit, if ever. I'm very happy with P3Dv5.1. And yes, it's been quite a while. I first got into FS in the Bruce Artwick days, before MS bought it and continued it. I started doing software for it at the FS4 stage (still a DOS program). FSUIPC started with FS98 and has had continuous development since then. But now at 77 I am retired from active development -- my son John has taken over the reins -- FSUIPC6 and FSUIPC7 are his babies. Good flying! Pete

Thanks Roman. Got me thinking -- maybe "DontLogThese" should be made Profile Specific? I'll mention it to John. Pete

Well I'm sorry, but I haven't a clue. If everything works in all other aircraft (including PMDG ones) then there must surely be something wrong with your DC-6 install. That thread actually talks more about how "BlueStar" got it to work, which does therefore suggest it is more to do with your specific DC-6 install. Hqve you uninstalled and re-installed it, in case? Have you checked for updates? Pete

It might be worth trying with the SimConnect menu controls instead of the numeric keypresses. i.e. SIMCONNECT MENU n where n runs from 0 to 9. Pete

That is ONLY installed on the desktop if you selected the option for it. As John says, if you don't want to use it just delete it! FSUIPC7.EXE and your MSFS are two separate programs. You can run one or the other independently if you wish. MSFS will work without FSUIPC7, and FSUIPC7 can be run without MSFS to set things up or just look around its options if you so wish. What exactly doesn't work for you? What have you used it for? It doesn't do anything by itself. If you wanted it to help with your controls you have to actually start assigning things in it. It's a tool for you to use, but you need to actually do something, as with any tool. There's ample good documentation supplied. I respectfully suggest you take a look and think about what you want to actually do with it before returning here. Then if you have any real problem explain exactly what it is and we can help. Pete

Version 5.02 of MakeRwys is now released. New files f4x.csv and f5x.csv are 8.33kHz compatible. The f4 and f5 files only contain 25kHz frequencies with 8.33 ones converted. Pete

Lots of folks having problems with the same throttle quadrant? All with the DC-6? How come you are the first here for support? I'm puzzled. First, let's separate the components: 1. Is it a problem ONLY with the DC-6 2. Or is it a problem with the Quadrant on multiple aircraft 3. Or is it a problem you have with the PFC driver (PFCcom64.dll)? So, no problem with the quadrant or the driver? Sorry, this is still confusing. Have you just changed to P3D4 and FSUIPC5? If so is the throttle not working at all in any aircraft? Or does the "never had a problem with throttles in any of my aircraft" comment apply to P3D4, and you only have a problem with the DC-6? Most PMDG aircraft don't like that route. you normally have to use the AXIS_THROTTLE in the FS control list instead. And they don't like FSUIPC calibration. Nothing works in the calibration? No changes, nothing happens at all? Sorry, but I still can't make head nor tail or what your problem is, exactly. Please also try to split your posts into separate paragraphs. it isn't easy to read one large block of technical text and make full sense of it. Pete

@Phil4125 Aha! Sorry, did not notice you were referring to the same product! Oops. Yes, a PM to Chuck100 should hopefully elicit help. Else I can try emailing him to look here. Pete

In that case you should have posted with a title which might be noticed by such a person. "Reserved Offset Request" is unlikely to. Does this hardware or software, whatever it is, use FSUIPC at all? Pete

You posted in a thread entitled Reserved Offset Request What does your question have to do with that? Or even FSUIPC or any software supported here? If you can't find the specific support forum or email address for your hardware or software (I've no idea what it is you are talking about!) I think you will probably need to post -- with more details AND a properly descriptive thread title -- on a more general forum, such as one of those on AVSIM, and hope that someone there recognises what it is. Pete

You are using an early unsupported version of MakeRunways. That problem was fixed within a couple of days of it first being reported! Pete

Sorry, here we aren't in the business of making controls. We are programmers, making software not hardware. Look for a cockpit builders Forum, maybe on AVSIM. Pete

Exactly. I was only thinking of your program, for folks with 25kHz radios if you are only going to support 8.33. Pete

Okay. I think so too ... I'll make an updated MakeRwys, probably for release tomorrow. Won't you need an option to cater for users with only 25kHz spacing radios? Pete

Addon programs, most usially ATC ones, using MakeRwys generated data files to get the COM frequencies (files f4.csv and f5.csv). Pete

I realised after starting to look at this that your first example is not a good one, as 120.625 is a valid 25kHz spacing frequency too, and normally shown as 120.62 on older radios. I'm in two minds here. If I change the f4.csv and f5.csv files to provide the full 6-dgit frequencies, this might mess up some less intelligent programs. Also, there are probably many folks (i am one such) with hardware radios which cannot deal with the 8.33kHz spaced frequencies. I am thinking of having two new files, f4x.csv and f5x.csv which have the 6 digits and the 8.33kHz frequencies, and converting all COM frequecies to 25kHz spacied ones in the existing f4 and f5 files. OR the other way around. Updating f4 and f5 for 8.33 and having new files with converted frequencies. What do you think? Pete

DC-6? Is that a new PMDG development? What flight simulator and FSUIPC version are you using? Is the PFC quadrant one of the serial port ones, using my PFCcom driver, or a normal USB joystick type, recognised as such by Windows? What exactly is the problem with setting up the throttles? Pete

I think MakeRwys is merely truncating them to xxx.xx format. I'm looking at fixing MakeRwys for 8.33, but for P3D5 tests I'd need to look for an airport using them. Would there be some add-ons with 8.33 being used, do you know?. Pete

I think you should be using SimConnect directly. It does exactly as you wish. You misunderstand what FSUIPC is for. For applications it is just a conversion interface or layer on top of SimConnect with the sole purpose of providing compatibility. The offset units and format were established initially by Microsoft and many of the ones in FSUIPC follow the layout used in FS98, especially those lower offsets where FSUIPC does conversions from the mostly double or float values provided by SimConnect into the forms used in FSUIPC over FS98, FS2000, FS2002, FS2004, FSX, FSX-SE and the P3D range. They already exist and work fine with P3Dv5, but Asobo as yet has not provided the facilities in SimConnect to handle them. Pete

Two questions: 1. What syntax is this? "sound.path([[C:\]]);". Surely that should be sound.path("C:\\") 2. Have you checked to make sure MSFS doesn't have exclusive access to your sound driver? With FSUIPC7 being a separate process, unlike in previous incarnations, that's a factor. BTW you don't need ; at the end of each statement in Lua. I know it's a habit from C/C++ and so on. It does no harm, just not needed. Pete