Jump to content
The simFlight Network Forums

FSUIPC6 does not generate radar.bin file


Recommended Posts

Hi,

I am running the Sim-Avionics suite in P3Dv4. I have had a fully functioning weather radar until upgrading to FSUIPC6. since upgrading to v6, the radar.bin file is no longer generated.

Here is my setup:

PC 1 > Instructor station (Sim-Avionics server, Wide FS, Active Sky P3Dv4)

PC 2 > Sim PC (Prepar3D 4.5.13.32097, FSUIPC 6.0.8)

PC 3 > Avionics PC (Avionics suite, WX folder to receive radar.bin from FSUIPC)

PC 2 has full read/write access to PC 3 WX folder hosting radar.bin file. (tested)

PC 2 FSUIPC6.ini has the following entry

[General]
ASNwxRadarPath=\\AVIONICS-PC\Sim-Avionics\WX\radar.bin

This path has been verified and worked fine in FSUIPC5.

Below is the FSUIPC log file. There is no indication that the radar.bin file is being generated. Any help to trouble shoot this issue would be much appreciated

Thomas

 

********* FSUIPC6, Version 6.0.8 (7th May 2020) by Pete & John Dowson *********
Prepar3D.exe version = 4.5.13.32097
Running inside Prepar3D v4
Module base=7FFDA3180000
Windows 10 Home 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0)
Reading options from "P:\Addons\Utilities\FSUIPC\FSUIPC6.ini"
Checking the Registrations now ...
User Name="hidden"
User Addr="hidden"
FSUIPC6 Key is provided
WideFS7 Key is provided
        0 System time = 13/06/2020 09:58:28
       15 FLT UNC path = "\\FLIGHTSIM\Documents\Prepar3D v4 Files\"
       15 Using DialogMode
       78 FS UNC path = "\\FLIGHTSIM\Prepar3D\"
      297 ---------------------- Joystick Device Scan -----------------------
      297 Product= CH FLIGHT SIM YOKE USB 
      297    Manufacturer= CH PRODUCTS
      297    Vendor=068E, Product=00FF (Version 0.0)
      312    GUIDs returned for product: VID_068E&PID_00FF:
      312       GUID= {3FA89710-8692-11E7-8003-444553540000}
      312       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255
      312 Product= CH PRO PEDALS USB 
      312    Manufacturer= CH PRODUCTS
      312    Vendor=068E, Product=00F2 (Version 0.0)
      312    GUIDs returned for product: VID_068E&PID_00F2:
      312       GUID= {3FA89710-8692-11E7-8002-444553540000}
      312       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      312 Product= Controller (XBOX 360 For Windows)
      312    Vendor=045E, Product=028E (Version 0.0)
      312    GUIDs returned for product: VID_045E&PID_028E:
      312       GUID= {D538EF10-393C-11E9-8001-444553540000}
      312       Details: Btns=10, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535
      312 Product= JetMAX 737 Throttle
      312    Manufacturer= TEKWorx Limited
      312    Serial Number= 00000212
      312    Vendor=1FD1, Product=0600 (Version 1.2)
      312    GUIDs returned for product: VID_1FD1&PID_0600:
      312       GUID= {3FA89710-8692-11E7-8001-444553540000}
      312       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X0,Y0,Z1023
      312 -------------------------------------------------------------------
      328 Device acquired for use:
      328    Joystick ID = 3 (Registry okay)
      328    3=CH FLIGHT SIM YOKE USB
      328    3.GUID={3FA89710-8692-11E7-8003-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 2 (Registry okay)
      328    2=CH PRO PEDALS USB
      328    2.GUID={3FA89710-8692-11E7-8002-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 0 (Registry okay)
      328    0=Controller (XBOX 360 For Windows)
      328    0.GUID={D538EF10-393C-11E9-8001-444553540000}
      328 Device acquired for use:
      328    Joystick ID = 1 (Registry okay)
      328    1=JetMAX 737 Throttle
      328    1.GUID={3FA89710-8692-11E7-8001-444553540000}
      328 -------------------------------------------------------------------
      469 ### Checking Prepar3D.cfg
      469     Controllers are set to ON, using RawInput within P3D
      469 -------------------------------------------------------------------
      469 LogOptions=00000000 00000001
      484 -------------------------------------------------------------------
      484 SimConnect_Open succeeded: waiting to check version okay
      484 Opened separate AI Traffic client okay
    54687 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.13.32097 (SimConnect: 4.5.0.0)
    54687 Generating controls file list: 'C:\Users\SIM_1\Documents\FSUIPC6\Controls List for P3Dv4 Build 32097.txt'
    54687 Initialising SimConnect data requests now
    54687 FSUIPC Menu entry added
    54703 ... Using Prepar3D with Academic License
    54719 \\FLIGHTSIM\Documents\Prepar3D v4 Files\Progress.fxml
    54734 \\FLIGHTSIM\Prepar3D\SimObjects\Airplanes\B777-300ER\B777-300ER.air
    54734 ### The user object is 'Boeing 777-300ER Singapore Airlines'
    54734 ### Mode is NORMAL
    55094 ### Mode: PAUSE on
   116172 Loading Complete ...
   116203 ### Mode is NORMAL
   116734 User Aircraft ID 1 supplied, now being used
   116734 Aircraft loaded: running normally now ...
   117375 System time = 13/06/2020 10:00:25, Simulator time = 08:59:24 (01:59Z)
   117406 Aircraft="Boeing 777-300ER Singapore Airlines"
   123375 -------------------- Starting everything now ----------------------
   123375 Starting WideServer now ...
   123484 ASN active function link set
   123484 Ready for ActiveSky WX radar with additional data
   124547 Advanced Weather Interface Enabled
   126687 Weather Mode now = Theme

 

 

 

 

Link to comment
Share on other sites

7 hours ago, thomas747400 said:

I am running the Sim-Avionics suite in P3Dv4. I have had a fully functioning weather radar until upgrading to FSUIPC6. since upgrading to v6, the radar.bin file is no longer generated.

There's no difference in the way this works in FSUIPC6 from FSUIPC5, except that it also accepts a link from the P3D5 version of Active Sky's installed DLL module. With P3D4 it is still the same. Which version of Active Sky are you currently using? 

FSUIPC merely contacts the Active Sky module asking to be sent the binary weather data which FSUIPC then just unceremoniously dumps into the nominated file.

Of course there's been a lot of concentration on P3D5 recently, rather neglecting P3D4 re-testing perhaps, so I will make a point of checking it on P3D4 this weekend.

Pete

 

Link to comment
Share on other sites

8 minutes ago, thomas747400 said:

I am using AS for P3Dv4 build 7410.

And was it the same build with FSUIPC5?

I think I need to update my P3D4 ActiveSky installation. The ActiveSky program is common to P3D4 and P3D5 but the crucial part for this, the installed DLL in P3D, is different.

Pete

 

Link to comment
Share on other sites

1 hour ago, thomas747400 said:

I updated AS P3Dv4 to the latest build today as a means of trouble shooting the issue. I did not take note of the previous AS build number but it was the same I successfully used with P3Dv4 and FSUIPC 5.

 
I've spent some time doing  thorough tests here on two separate systems, one with only P3D4 installed, and the other with both P3D4 and P3D5..
 
ASP4 build 7459 works perfectly with P3Dv5 HF1.
ASP4 build 7459 does not work properly with P34Dv4, version 4.5.13.
 
The problem appears to be that the flag provided by the ASP4 internal interface to show whether ASP4 is connected or not remains FALSE (ie untrue). This means FSUIPC doesn not request the Call Back which provides the radar data.
 
I have conclusively proven this by tracing through the code in FSUIPC6 in identical ways in P3D4 and in P3D5.  The path is in fact identical in both cases with the small difference that the name of the Module to be used for P3D4 is as_connect_64.dll whereas for P3D5 it is as_connect_v5.dll.  That is determined properly and set is proven by the fact that all of the functions it provides are then available to FSUIPC.
 
I am therefore convinced it is a bug introduced during Active Sky's developments for P3Dv5. I have accordingly written to my contacts in HiFi with my full analysis. i will advise as soon as i receive a response.
 
I had thought of possibly going ahead with asking for the data even if the indication is that ASP4 is not connected. Possibly the wrong indication is merely an oversight and in fact the data is all still available. I might experiment with that tomorrow. What would worry me is what might happen if, in fact, ASP4 was genuinely not connected.
 
Pete
 
 
Link to comment
Share on other sites

19 hours ago, Pete Dowson said:

Possibly the wrong indication is merely an oversight and in fact the data is all still available. I might experiment with that tomorrow.

That doesn't work. If doesn't indicate that it is running, it doesn't provide radar data either.

HiFi are checking for me. So far they think it might be an installation problem. but I did the same for P3D4 as for P3D5 when installing the updates, and P3D5 radar images are fine.

Exchanges with HiFi are slowed by the time difference. I'm in the UK, they're in California I think.

Pete

 

Link to comment
Share on other sites

On 6/14/2020 at 12:49 PM, Pete Dowson said:

HiFi are checking for me. So far they think it might be an installation problem. but I did the same for P3D4 as for P3D5 when installing the updates, and P3D5 radar images are fine.

After some problems here (my development system suffered a fatal crash, which I'm in the process of recovering from), i managed to test the WX Radar facilities with the latest Beta of Active Sky (released within the last couple of days -- sorry I don't have access to the build number at present). That works only with P3D4.5.14 (= HF3, the last update), and the radar image is perfect with that combination.

Note that ActiveSky is now quite complex. There are three parts -- the ActiveSky program itself, plus a program called "ActiveSkyUtils.exe", plus the module in P3D (AS_CONNECT_64.DLL). All three must be running okay.

If you still get problems i suggest you use the "Log" option in the main ActiveSky options to generate logged details and send them off to ActiveSky.

I can assure you that all is well in FSUIPC.

Pete

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.