Pete Dowson

I am obviously word not allowed (why on Earth is "i-g-n-o-r-a-n-t" a "word not allowed"? How much of normal English is not allowed in these forums? What sort of Censors are living here?) of what those problems are, because that video seems to be to be a good example of what a good sim it is. The only "off" thing I noticed was at the end whilst you were taxiing to park, and that was a flickering white edge to some of the trees and other objects. That was after more than 10 minutes during which i could spot nothing wrong! Should I have? I have not been using EA at all in P3D5. As an airliner flyer I never liked it. Looked good from below cloud, but terrible at cruise altitude. And mostly it made my world too gray -- less colour in everything, and too dark. Maybe I'll try it again with 5.1, though the criticisms here put one off. But not your video. Was it intended to? Pete

Of course. As Dave points out, it can only read what is implemented. In fact that's the main point of the program -- telling applications how it is implemented, not how it should be implemented! Pilot2ATC wants to be able to direct you on the taxiways you actual have in MSFS. If it used non-matching real world data, perhaps from Internet sources or Navigraph charts, then you wouldn't be able to follow those instructions in MSFS! Pete

Are you saying it is incorrect, that the scenery data in MSFS is bad? Do make sure you are using the latest version of MakeRwys 5.00BETA. The taxiway data was corrected in BETA3 (important changes). We're now up to BETA4 (just minor changes). Pete

Taxiways were being generated with bad coordinates in MakeRunways Beta2. Please make sure you use Beta3, released this morning. Pete

A Beta version of MakeRunways which works with MSFS is now available on Open Beta: MakeRunways Beta version 5.00 for MSFS Pete

A Beta version of MakeRunways which works with MSFS is now available on Open Beta: MakeRunways Beta version 5.00 for MSFS Pete

I thought the "OCI" term (One click install) referred to the file structure where a complete airline schedule and the aircraft it needs, along with their liveries, is all installed when selected in the control program (the "one click" on the airline to select it). The non-OCI airlines and require a lot more work from the user. Pete

I'm afraid I can't help with the G1000 particularly, but the plan format supported by MSFS is the standard FSX .PLN XML format (i.e. .PLN filetype). And for loading via the MSFS "World" option it doesn't matter where you put it as it comes up with a normal Explorer windows so you can go to whatever menu you like. I don't know if loading a plan or even planning a flight, in the World menu also loads it into the G1000, but it's worth a try assuming you haven't already. I know it works for the ATC and Copilot. Pete

It works well for me. Pete

I just use the Auto option so it chooses the SID, STAR and Approach. I take no notice of it till I get the relevant clearance which, for the STAR and approach does occur en route (by TOD if I remember correctly), and if the weather has changed significantly this can be different from the one it originally selected. I think there's an option to make it pilot choice only, not ATC, but I don't use that as I don't think it is realistic. Except on short flights I don't complete the flight plan in the FMC till I get the clearance. On short flights I do check the plan and enter it as I assume the weather won't change that much and it can get quite hectic unless i have a copilot visiting. Pete

I think you certainly need permission to change altitudes -- you shouldn't descend without AFAIK. Pete

I just don't have enough information, nor do I know how to find it at present. I used to simply hack into binary files to work things out, but my abilities in this direction have simple dissipated as I've got older (I'm over 77 now, and feeling it). This is why I handed the business part (FSUIPC) over to my son John. But there is so much to do all the time with MSFS developments there that there is no way I'd ask him to take on a freeware project like MakeRunways, In the meanwhile you should find the MakeRunways files generated for FSX or P3D reasonably usable for ATC, just not for autopilot control etc. Pete

MakeRwys does not work with MSFS. Sorry, but this area of development is still a long way off. Pete

He did report it there, but since the error message presented was one from P2A, not from FSUIPC, he was sent back here. Like myself before him, he is not really able to support third party program failures. The user did point on there that FSUIPC was still running normally. If FSUIPC had crashed we'd have asked for details of that crash and the log leading to it. So far, FSUIPC7 itself is proving very stable. What is certainly not stable is the interface with Simconnect which is giving many folks problems with controls disconnecting. However, i don't think these would mess up P2A, on the flying! The error #9 "FSUIPC_ERR_NOTOPEN" just means that a call to process data couldn't execute because the link to FSUIPC hasn't been or is no longer opened. If FSUIPC crashed one would probably expect a timeout, though i suppose Windows might be clever enough to auto-clear the link itself. Not sure. does P2A retry opening the link at all? It probably should do on such an error. Retrying the process operation again would be pointless. As a test, and to be fully sure that it should certainly connect okay, I would wait before starting P2A until the aircraft is definitely read to fly. However, programs can connect to FSUIPC7 and deal with the interface even without MSFS running. Whether P2A would get results back which would lead it to declare "connected" depends on what it checks I suppose. I think almost everything read would probably be zero (except those things local to FSUIPC, like the version). Pete

Assuming you bought a registration for WideFS and entered it into your FSUIPC7.KEY file as in the instructions, then there's some access problem. But you'll need to ask on the FSUIPC support forum and supply log files -- FSUIPC7.LOG, WideServer.LOG and WideClient.LOG. FSUIPC7 is 3 complete versions later than FSUIPC4 and 14 years later. There can be no discount really. Incidentally, it is John Dowson's product, not mine. Pete

The FSUIPC7 free Beta key file is supplied in the ZIP. You just need to copy the contents of the ZIP into a folder of your choice (eg, in my case, E:\FSUIPC7). You must have done that automatically, Dave, without thinking about it. Pete

You can set it to auto-connect -- and auto-close when MSFS does if you wish. You can start FSUIPC before MSFS or after. it's quite flexible. Pete

Surely you haven't changed completely to MSFS already? It's no decent replacement yet for P3D. Not even for FSX. Pete

Before adding to a thread surely you should read it and see what'sbeen said already? Because the question is asked and answered several times. In fact it is asked and answered (regarding ALL programs seriously using SimConnect, not just FSUIPC)in the MSFS forums, and even the FSUIPC forum! We all hoping that the fix ASOBO have promised for about 6 days time will sort it! Pete

Only the separate SimConnect.DLL is now built into FSUIPC7 -- to save users finding that module and copying it into the same folder. But that is only the interface code. SimConnect itself, the part which actually does anything, is all part of MSFS, and currently there's some bug which causes serious performance issues (which weren't there before the released version!). Hopefully it will be fixed within the next 7 days, at least according to the announcement yesterday. Pete

I don't think you need to actually purchase FSUIPC in order to use any application, unless it needs Lua plug-ins or assignments in FSUIPC. It's nice of folks to buy it, and this is encouraged of course, but its use as an interface for applications has always been free to end users. Income was originally derived from the application producers or sellers instead. But that became too difficult to police and liable to be unfair to folks try to make some money just to cover costs. So that became voluntary too. Pete

Yes. I always put the version number or similar in the filename, so the links would be different each time. John prefers to do it differently. And he doesn't tend to update version numbers for Beta releases, so you might only see the date of the build changing. (I used to run out of version numbers, as with "FSUIPC3.999z9", so I can't blame him, especially with something like MSFS which, hopefully, will be evolving rapidly). Pete

Same as before. Links are in the Announcement: https://forum.simflight.com/topic/90193-fsuipc7-beta-for-msfs/ Pete

None of that is needed with the latest version of FSUIPC7. ASOBO actually released the static library the day after the release, and so it is now built into FSUIPC. Download the current FSUIPC7 and delete the Simconnect.DLL you placed in its folder. Oddly enough they also gave permission for us to include SimConnect.DLL in our packaging, nor that we no longer need it! 😉 Yes. this affects ALL SimConnect applications. It's very annoying as the last Beta we received worked fine, still smooth, even with several client applications. Developers never saw a release candidate. Pete

That's not entirely true, though it is for folks with eyesight like mine (and possibly a lot of old folks). I'm quite happy with my system set at 30 fps (with 2 x 4K projectors and a curved 200 degree FOV screen). In fact I'be okay okay with 25 but that isn't my projectors natural setting (whilst 30 fps is). This is an interesting read: https://www.quora.com/Why-are-movies-shown-in-24fps-while-60fps-looks-more-real#:~:text=24 frames per second was,shooting 60 frames per second.&text=Over time our eyes have,to 60 frames per second. Pete