Another radar gauge for VC & Window usage

[roland_lfor 245]

6 hours ago, jabloomf1230 said:

Well, is there any possibility that you could make the gauge work with ASP 3D for P3d5?

I've not yet downloaded ASP3D, did you try the gauge with it?
Is there changes in API?

[jabloomf1230 2,445]

Yes, I got a black screen and none of the gauge's adjustment locations work. The cursor changes shape so the gauge is installed. I'll do more detailed tests later today. The AS connector file has a different name than in ASP4. 

[roland_lfor 245]

Ok thanks, I'll have a look but I can't give you a time frame.

I hope I still have the project files

Edited May 8, 2020 by roland_lfor

[roland_lfor 245]

I was able to get back the old x64 project and load it into VS2019, so it's a good starting point 

[Gridley 257]

Was just thinking of trying the same thing!  Jay, you're always one step ahead of me!  Roland - good luck with the update!

Best,

sg

[Gridley 257]

Also, just an FYI - it appears REX/Milviz have decided not to update their product any longer:

 

[roland_lfor 245]

Oh Oh !

In the meantime, if you wish to test the new Radar gauge Build for ASP3D and P3Dv5 - at your own risk -you will find a direct download link in this thread @ HiFi forum:

https://forums.hifisimtech.com/threads/free-wx-radar-gauge-for-popup-or-vc-integration-x64-p3dv4-build.8594/post-54031

 

[JRBarrett 3,070]

2 minutes ago, roland_lfor said:

Oh Oh !

In the meantime, if you wish to test the new Radar gauge Build for ASP3D and P3Dv5 - at your own risk -you will find a direct download link in this thread @ HiFi forum:

https://forums.hifisimtech.com/threads/free-wx-radar-gauge-for-popup-or-vc-integration-x64-p3dv4-build.8594/post-54031

 

I will certainly give this a try!

 

[Mroberts95 136]

57 minutes ago, roland_lfor said:

Oh Oh !

In the meantime, if you wish to test the new Radar gauge Build for ASP3D and P3Dv5 - at your own risk -you will find a direct download link in this thread @ HiFi forum:

https://forums.hifisimtech.com/threads/free-wx-radar-gauge-for-popup-or-vc-integration-x64-p3dv4-build.8594/post-54031

 

I imagine this only works in the old weather version and not the new EA version of weather correct?

[roland_lfor 245]

It seems to work - radar displays rain area - but as HiFi explained, the rain areas are less accurate in EA.

[RamonB 449]

Thank You Roland.
Will give this new version a try ASAP.

[JRBarrett 3,070]

30 minutes ago, roland_lfor said:

It seems to work - radar displays rain area - but as HiFi explained, the rain areas are less accurate in EA.

Roland,

I downloaded the new DLL and placed it in the gauges folder. I referenced it in in the panel.cfg for the default Commander 114 as follows: (The first free window is #4).

[Window04]
size_mm=100,150
position=2
visible=1
Window_pos=0.05,0.65
zorder=4
background_color=16,16,16 
alpha_blend=0.55
gauge00=RolasnRadar!oRadGauge, 0,0,100,150, sweep|beam|icing

(That was from the PDF instruction document for your original version).

My default startup scenario uses the Commander 114. After making the change, if I try to start P3DV5 HF1, the scenario start screen never appears. After the initial P3D spash screen, the simulator disappears completely - but if I check the running processes in Process Explorer, I can see that Prepar3d.exe is still running - but I have no way to display it, and have to manually kill the process.

If I change the default startup scenario to the F35, P3D loads fine. If I then choose the Commander 114 (once the sim is running), it loads without a crash, but when I try to select the radar with SHIFT-5, I only see a semi-transparent gray box - there is nothing in it.

When I hover over the new DLL in Windows Explorer, it says that it is version 1.0.0.1. The DLL from 2017 in your original package downloaded from the Avsim file library is version 2.0.0.0

Jim Barrett 

[roland_lfor 245]

Let 

17 minutes ago, JRBarrett said:

Roland,

I downloaded the new DLL and placed it in the gauges folder. I referenced it in in the panel.cfg for the default Commander 114 as follows: (The first free window is #4).

[Window04]
size_mm=100,150
position=2
visible=1
Window_pos=0.05,0.65
zorder=4
background_color=16,16,16 
alpha_blend=0.55
gauge00=RolasnRadar!oRadGauge, 0,0,100,150, sweep|beam|icing

(That was from the PDF instruction document for your original version).

My default startup scenario uses the Commander 114. After making the change, if I try to start P3DV5 HF1, the scenario start screen never appears. After the initial P3D spash screen, the simulator disappears completely - but if I check the running processes in Process Explorer, I can see that Prepar3d.exe is still running - but I have no way to display it, and have to manually kill the process.

If I change the default startup scenario to the F35, P3D loads fine. If I then choose the Commander 114 (once the sim is running), it loads without a crash, but when I try to select the radar with SHIFT-5, I only see a semi-transparent gray box - there is nothing in it.

When I hover over the new DLL in Windows Explorer, it says that it is version 1.0.0.1. The DLL from 2017 in your original package downloaded from the Avsim file library is version 2.0.0.0

Jim Barrett 

Let me see... that's correct.

Actually I moved the C++ project to Visual Studio 2019 and I did not changed the default version number.

But if you open the Dll Properties/detail window you will see that "Product name : for P3D x64" so that's the one I've build last week.

I'm using the same in the A2A Cherokee right now without trouble (P3D v2 HF1 and ASP3D Beta 2).

>>>>> Check that you installed the redistributable for VS2019 x64

Edited May 12, 2020 by roland_lfor

[roland_lfor 245]

Actually there is NO change in the code itself. I've only changed the module string called to match the new HiFi Dll name.

I believe one can do a dirty hack on PMDG or Majectic Q400 Dll involved in weather radar, simply using an Hexa editor and find/replace the old module name by the new one, because luckily both have the exact same characters number  (as_connect_64 >> as_connect_v5)

[JRBarrett 3,070]

13 minutes ago, roland_lfor said:

Let 

Let me see... that's correct.

Actually I moved the C++ project to Visual Studio 2019 and I did not changed the default version number.

But if you open the Dll Properties/detail window you will see that "Product name : for P3D x64" so that's the one I've build last week.

I'm using the same in the A2A Cherokee right now without trouble.

>>>>> Check that you installed the redistributable for VS2019 x64

I checked the properties window for the DLL, and it does show “P3D x64”.

My installed VS runtimes for VS 2015, 2017 and 2019 both x86 and x64 are at version 14.25.28508, which is the very latest.