Hi,I did a search on the forum and did not find any information/questions about RC5 and the ability to use it with P3D, just wondering if RC5 is going to be made available/compatible with Prepar3D.Thanks

I did a search on the forum and did not find any information/questions about RC5 and the ability to use it with P3D, just wondering if RC5 is going to be made available/compatible with Prepar3D.

There should be no difference. The current version of FSUIPC4 works with Prepar3D versions 1.0, 1.1 and 1.2. I am pretty sure RC won't need anything else other than its airport data.At present if you've added scenery layers you'll need to copy the SCENERY.CFG file back from C:ProgramDataLockheed-MartinPrepar3D (or the XP equivalent in AllUsers) back to the Prepar3D main folder and run MakeRunways there to build the databases. I will update MakeRunways at some stage to find the file automatically, but I've not done that yet.RegardsPete

and while we're at it, what is the status of version 5? :)

I didn't want to go there as I've given that dream up.

Hi Pete,I have been unable to get Radar Contact to work with Prepar3D. I get the following error: Maybe running on WideClient, but FS not running on Server, or wrong FSUIPC. I am running RC4 via network. I have been able to get ActiveSky Evolution, WideFS and FTG-ACARS working via network. I'm using WideFS ver. 6.8.6.0.Thanks

I have been unable to get Radar Contact to work with Prepar3D. I get the following error: Maybe running on WideClient, but FS not running on Server, or wrong FSUIPC. I am running RC4 via network.

Hmm. Sounds like it is checking the FS version number, and so refusing to run. Which is a bit daft of it really. It should simply check for >= its required level.Try using the "spoofing" facilities in FSUIPC + Lua to make the FS version number read as if it is FSX. A plug-in like this should do:

-- Loop foreverwhile 1 do   ipc.writeStruct(0x0024, "1UW", 0x3308, "1UW", 2, "1UW", 8)   -- Sleep for 50 mSecs so the update gets done roughly 20 times per second   ipc.sleep(50)end

I'm not in a position to test this at present, so please try it and let me know. All it is doing is telling FS to supply the value '8' when anything reads offset 3308, the FS version number (which will be 10 for P3D I think). '8' means FSX.Save the file as "SayImFSX.lua" (for example) in your P3D Modules folder, and add[Auto]1=lua sayimfsxto your INI file (or add another line if you are already using [Auto]). Alternatively you could save it as ipcReady.lua, whch needs no [Auto] section.RegardsPete

Hi Pete,Not sure if I did this right:1. I made a file called SayImFSX.lua and placed the following within it. I then added the file to my Prepar3D/Modules sub-folder.-- Loop foreverwhile 1 do ipc.writeStruct(0x0024, "1UW", 0x3308, "1UW", 2, "1UW", 8) -- Sleep for 50 mSecs so the update gets done roughly 20 times per second ipc.sleep(50)end2. I added the following to my FSUIPC.INI file.[Auto]1=lua sayimfsxI get the same error message, did I miss anything?.Thanks

I get the same error message, did I miss anything?.

One of three things:1. Maybe your FSUIPC4 is out of date? The Lua works here okay using FSUIPC 4.747. There was a problem earlier with [Auto] not always operating.2. The Lua does not start and do its job until FSUIPC is fully ready to fly. Don't start RC before then.3. If neither of the above then RC is checking something else. We'd need comment from JD.RegardsPete

Hi Pete,The FSUIPC version installed is 4.745, dated 2nd November 2011. I also noticed that there is a new entry within FSUIPC4.INII added the following[Auto]1=lua sayimfsxAnother entry was automatically entered below my Auto entry called[LuaFiles]1=SayimFSXI started Prepar3D and waited until it was completely loaded before I ran WideFS and then RC4. WideFS shows its connected to Prepar3D, but I get the same error message that is shown above when trying to connect RC4.I'm going to download version 4.747 if I can find it on the website and try again.UPDATE: I downloaded the latest version from the website, but it says its version 4.745 not 4.747.Thanks

The FSUIPC version installed is 4.745, dated 2nd November 2011.

That should be okay.

Another entry was automatically entered below my Auto entry called[LuaFiles]1=SayimFSX

Yes -- I'm very surprised you've never used any Lua plugins before. They are all catalogued in that section so their reference number can be used in button and key assignments.

I started Prepar3D and waited until it was completely loaded before I ran WideFS and then RC4. WideFS shows its connected to Prepar3D, but I get the same error message that is shown above when trying to connect RC4.

It is starting to sound like RC4 is checking something else too.

I'm going to download version 4.747 if I can find it on the website and try again.UPDATE: I downloaded the latest version from the website, but it says its version 4.745 not 4.747.

When you say "the website" I assume you mean the Schiratti site? All my latest versions are always hosted in the Download Links subforum on my Support Forum. There's lots of other goodies there too. I'm surprised you've never been. (It might be 4.748 by now. I don't recall without checking).The Schiratti site isn't in my control and I can't update it nearly every day like I do on my own Forum site.I do have P3D installed on my cockpit PC. I'll try RC with it and this fiddle tomorrow. Out tonight.RegardsPete

Hi Pete,Thanks, I appreciate all the help. I've upgraded FSUIPC to 4.747 and WideFS to 6.8.9.9, but I still have the same problem.Thanks again for all the help Pete, I'll check back again tomorrow.

Thanks, I appreciate all the help. I've upgraded FSUIPC to 4.747 and WideFS to 6.8.9.9, but I still have the same problem.

RCV4 works perfectly here with Prepar3D, including via WideFS. In fact you don't need that fiddle for the FS version number so you can take those changes I gave you out now. RCV4 does read the version number, but it is quite happy with version "10". Seems it probably just checks for 7 (FS9) or greater, so it's okay with FS9, FSX, ESP and P3D.So, it sounds instead that you do not have a Connection. does the Wideclient title bar say it is connected? Does Prepar3D's title bar say there's a connection?You said

I have been able to get ActiveSky Evolution, WideFS and FTG-ACARS working via network. I'm using WideFS ver. 6.8.6.0.

but of course ASE uses Simconnect not WideFS. I don't know FTG-ACARS.You aren't running WideClient and RCV4 at different privilege levels are you? i.e. one "as administrator"? That'll stop them talking.The WideClient and WideServer log files will be needed next if you can't figure it out.[LATER]I've now updated MakeRunways so it finds the correct SCENERY.CFG file in ESP and Prepar3D as well and FSX and before. The updated version in 4.51.http://fsuipc.simflight.com/beta/MakeRunways_451.zipRegardsPete

Hi Pete,WideFS states its connected on the client machine, but I do not see any text within P3D that states its connected. I just got done reviewing the log file for WideFS and it shows the following.Connection made okay!Connection closed by server!This repeats over-and-over again, so I've got a connection problem. I've never had a problem in the past with FSX, not sure what's causing this.

WideFS states its connected on the client machine, but I do not see any text within P3D that states its connected.

You'd need to switch to windowed mode to see the title bar. It should say either "waiting for clients" or "connected" with the number of clients.

I just got done reviewing the log file for WideFS and it shows the following.Connection made okay!Connection closed by server!

That must be the Wideclient log, not "WideFS log" (there isn't one of those). The other half of the story is the WideServer log in the P3D Modules folder.

This repeats over-and-over again, so I've got a connection problem. I've never had a problem in the past with FSX, not sure what's causing this.

Make sure that nothing else is using the same ports that WideFS needs -- 8002 and 9002. Check the SimConnect xml and cfg settings in case that's using one of these.You can change the WideFS ports too, but you have to do it in both FSUIPC4 init and all the WideClient INIs.RegardsPete

Hi Pete,The only thing I'm running on the network is simconnect, its on port 500. Here are both log files.********* WideServer.DLL Log [version 7.747] *********Blocksize guide = 4096 (double allowed)Date (dmy): 18/11/11, Time 12:14:18.907: Server name is MIKE-PC 15725 Initialising TCP/IP server 15725 Initialising IPX/SPX server 15725 IPX/SPX socket() failed [Error=10044] Socket type not supported 15725 Failed to start IPX/SPX Server 15725 Initialising UDP/IP server 16115 Broadcasting service every 1000 mSecs------------------------------------------------------------------------------------------------********* WideClient Log [version 6.899j] Class=FS98MAIN *********Date (dmy): 18/11/11, Time 12:14:37.090: Client name is MICHAEL-PC 328 Attempting to connect now 328 LUA: "C:Program FilesWide ClientInitial.LUA": not found 328 Trying TCP/IP host "192.168.0.40" port 8002 ... 328 ... Okay, IP Address = 192.168.0.40 453 Connection made okay! 578 Connection closed by server! 578 Attempting to connect now 578 Connection made okay! 891 Connection closed by server! 891 Attempting to connect now 891 Connection made okay! 1203 Connection closed by server! 1203 Attempting to connect now 1203 Connection made okay! 1516 Connection closed by server! 1516 Attempting to connect now 1516 Connection made okay! 1828 Connection closed by server! 1828 Attempting to connect now 1828 Connection made okay! 2141 Connection closed by server! 2141 Attempting to connect now 2141 Connection made okay! 2453 Connection closed by server! 2453 Attempting to connect now 2453 Connection made okay! 2766 Connection closed by server! 2766 Attempting to connect now 2766 Connection made okay! 3078 Connection closed by server! 3078 Attempting to connect now 3078 Connection made okay! 3391 Connection closed by server! 3391 Attempting to connect now 3391 Connection made okay!The above runs in a continuous loop of connecting/Disconnecting.