Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Black screen, re-installed = error

Featured Replies

Hi, I've been away and re-visiting P3Dv4.5.  I tried to run the Lear 35 and the Falcon, but was getting a black screen. Uninstalled, download the installer from Just Flight website, copied serial to clipboard and was getting an error when selecting the plane. I get the same error with both Flysimware planes.

I suspect this may have something to do with the purchased version of Weather Advantage app?  But, I don't want to mess around if it is the Weather Advantage app since it works fine in my purchased copy of Milviz 310. Seeking advice...

P.S. I also have all the RealityXP avionics installed and working properly in the Milviz 310. Those are also installed in both Flysimware planes.

spacer.png

Edited by bofhlusr

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

3 hours ago, bofhlusr said:

I suspect this may have something to do with the purchased version of Weather Advantage app?  But, I don't want to mess around if it is the Weather Advantage app since it works fine in my purchased copy of Milviz 310. Seeking advice...

The WX radar works in the Lear and Falcon50 for me in P3D4.5. It has been a couple of years since I've used P3D, but just tried it. I tired to see what version of the WX radar I had but could not determine that. I no longer recall many P3D details I'm afraid.

If you want to experiment a bit with your WX radar version, you could make a backup copy of all your Milvix WX Radar files first so you have something to go back to if necessary.

Did the WX radar previously work for you in the Lear and Falcon in P3D4.5?

Your panel.cfg files for the Lear and Falcon should have some WX radar entries. For example, here are just the WX radar related entries in my Falcon50 panel.cfg file:

[Window Titles]
...
Window05 = WX Advantage Radar
...

[Window05]
ident = 71
visible = 0
sizeable = 1
size_mm = 419,381
position = 0
window_size = 0.343511450381679,0.556719107690809
window_pos = 0,0
gauge00 = MV_WX!WX2D,0,0,419,381,1
gauge01 = MV_WX!WX,64,121,291,205,1
gauge02 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

.....

[Vcockpit30]
Background_color = 0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$MV_WXM
gauge00=MV_WX!WX,  0,0,512,361
gauge01 = CONTROL_PANEL!clipboard RADAR,  0,0,512,361

Also, I have a MV_WX.dll file in my P3Dv4 gauges folder.

Al

Edited by ark

  • Author

Hi Ark, yes. WX radar previously worked for these two planes. It was perfect. In fact, it's still working now on the purchased copy of Milviz's 310.  

I recently unsuccessfully tried to run the Lear 35 and the Falcon 50.  A URL error of some kind. Browsing the forum indicate that apparently Flysimware had new installers (why?). That led to a re-install for both planes. I suspect this error might be DRM related. 

I'm going to try your suggestion. I'll see if I can restore from a disk image backup. Thank you.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Author
On 3/30/2023 at 4:12 PM, ark said:

The WX radar works in the Lear and Falcon50 for me in P3D4.5. It has been a couple of years since I've used P3D, but just tried it. I tired to see what version of the WX radar I had but could not determine that. I no longer recall many P3D details I'm afraid.

If you want to experiment a bit with your WX radar version, you could make a backup copy of all your Milvix WX Radar files first so you have something to go back to if necessary.

Did the WX radar previously work for you in the Lear and Falcon in P3D4.5?

Your panel.cfg files for the Lear and Falcon should have some WX radar entries. For example, here are just the WX radar related entries in my Falcon50 panel.cfg file:

[Window Titles]
...
Window05 = WX Advantage Radar
...

[Window05]
ident = 71
visible = 0
sizeable = 1
size_mm = 419,381
position = 0
window_size = 0.343511450381679,0.556719107690809
window_pos = 0,0
gauge00 = MV_WX!WX2D,0,0,419,381,1
gauge01 = MV_WX!WX,64,121,291,205,1
gauge02 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

.....

[Vcockpit30]
Background_color = 0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$MV_WXM
gauge00=MV_WX!WX,  0,0,512,361
gauge01 = CONTROL_PANEL!clipboard RADAR,  0,0,512,361

Also, I have a MV_WX.dll file in my P3Dv4 gauges folder.

Al

Hi Al,

I restored from a disk-image, the two folders (for the Falcon and Learjet) from a few months ago and managed to get the two planes on screen and working except that the WX radar did not work.

So, I uninstalled and re-installed after downloading the install file for both planes from the Flysimware and Just Flight website.  But now, I'm back to the same dark screen and  "This WX is locked" error. 

I made sure I have the same entries as you have above and the correct file in the gauges folder.

Any other suggestion on why it's not working? It was working perfectly a few months ago and nothing has changed since then.



 

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

7 hours ago, bofhlusr said:

I'm back to the same dark screen and  "This WX is locked" error. 

By dark screen do you mean just the WX radar screen, or your whole monitor screen? In other words, does everything seem to work except the WX radar after reinstalling the latest version of the planes?

 

Al

 

Edited by ark

  • Author

Just the black screen for the whole monitor.

This happens after I launch P3D, run a default F-22 Raptor, change vehicle to the Lear 35, and all I hear is the engine running. The only way to exit the dark screen is to press the Esc button and select another plane but this results in a CTD.

Before pressing the Esc key, pressing the Alt-Tab gets me this. Note the error message:  "This WX is locked". 

Appended below after the screencap, is a copy of the panel.cfg and the aircraft.cfg file. Also appended is an image of my MV_WX.DLL file in the gauges folder.

As a side note, the purchased version of Milviz's 310 and the purchased version of the WX radar in it work perfectly. I'm thinking that it can't be a radar issue since it works fine in the Milviz 310.

The Lear 35 worked perfectly in P3Dv4.5 the last time I used it a few months ago. Since then nothing has changed or been added to P3D.

spacer.png

 

 

============================PANEL.CFG==========================
 

//--------------------------Designed by FLYSIMWARE! 2017------------------------------

[Window Titles]
Window00=CONTROL_PANEL
Window01=AIRCRAFT_OPTIONS
Window02=Reality XP GTN Unit 1 (managed)
Window03=Reality XP GTN Unit 2 (managed)
Window04=START_INSTRUCTIONS
Window05=DOOR_INSTRUCTIONS
Window06=PAYLOAD_MANAGER
Window07=WX Advantage Radar


[Window00]
file_1024=Control_Panel.bmp
size_mm=1024,1876
window_size=0.27
position=3
BACKGROUND_COLOR=0,0,0
visible=1
ident=CONTROL_PANEL

gauge00=CONTROL_PANEL!clipboard fuel repair,    50,320,340,320
gauge01=CONTROL_PANEL!clipboard map,            50,650,340,300
gauge02=CONTROL_PANEL!clipboard atc,            50,965,340,280
gauge03=CONTROL_PANEL!clipboard GPS,            50,1250,340,220
gauge04=CONTROL_PANEL!clipboard CABIN LIGHTS,   490,465,35,35
gauge05=CONTROL_PANEL!clipboard LUGGAGE LIGHTS, 490,530,35,35
gauge06=CONTROL_PANEL!clipboard DOOR LIGHTS,    490,595,35,35
gauge07=CONTROL_PANEL!clipboard kneeboard,      445,1005,530,400
gauge08=CONTROL_PANEL!clipboard OPTIONS,        485,1760,520,110
gauge09=CONTROL_PANEL!clipboard COLDDARK,      550,800,300,70
gauge10=CONTROL_PANEL!clipboard HOTSTART,       550,870,300,70


[Window01]
file_1024=spec_sheet.bmp
size_mm=1050,1050
window_size=0.55
position=5
BACKGROUND_COLOR=0,0,0
visible=0
ident=AIRCRAFT_OPTIONS

gauge00=CONTROL_PANEL!clipboard DOOR,           302,117,94,113
gauge01=CONTROL_PANEL!clipboard baggage,        380,299,68,41
gauge02=CONTROL_PANEL!clipboard baggage image,  453,253,145,87
gauge03=CONTROL_PANEL!clipboard pilot,          928,471,72,57
gauge04=CONTROL_PANEL!clipboard pilot2,         757,471,72,57
gauge05=CONTROL_PANEL!clipboard headset,        846,497,64,49
gauge06=CONTROL_PANEL!clipboard sunglasses,     846,471,64,21
gauge07=CONTROL_PANEL!clipboard wheel chocks,   131,254,62,44
gauge08=CONTROL_PANEL!clipboard PLUGS,          715,85,220,90
gauge09=CONTROL_PANEL!clipboard pilot image,    881,317,155,145
gauge10=CONTROL_PANEL!clipboard pilot2 image,   718,317,155,145
gauge11=CONTROL_PANEL!clipboard Shades,         332,400,123,62
gauge12=CONTROL_PANEL!clipboard FUEL QUANTITY,  0,0,1050,1050
gauge13=CONTROL_PANEL!clipboard FUEL MAP 1,     311,885,430,30
gauge14=CONTROL_PANEL!clipboard FUEL MAP 2,     311,885,430,30
gauge15=CONTROL_PANEL!clipboard FUEL ENG 1,     369,973,57,28
gauge16=CONTROL_PANEL!clipboard FUEL ENG 2,     628,973,57,28
gauge17=CONTROL_PANEL!clipboard FUEL XFER L,    290,801,164,108
gauge18=CONTROL_PANEL!clipboard FUEL XFER R,    598,801,164,108
gauge19=CONTROL_PANEL!clipboard OPTIONS,        13,12,427,72
gauge20=CONTROL_PANEL!clipboard START INST,     17,524,161,75
gauge21=CONTROL_PANEL!clipboard GPU,            840,208,181,85
gauge22=CONTROL_PANEL!clipboard DOORLOCK,       373,235,37,37
gauge23=CONTROL_PANEL!clipboard DOOR INST,      188,524,161,75
gauge24=CONTROL_PANEL!clipboard PAYLOAD,        17,352,161,75


[Window02]
size_mm=100,100
window_pos=0.378418,0.294271
window_size=0.243164,0.411458
// gj changed
visible=0
always_visible=0
zorder=99
background_color=0,0,0
ident=15751
gauge00=rxpGTN!GTN_750_1, 0, 0,100,100


[Window03]
size_mm=100,100
window_pos=0.378418,0.705729
window_size=0.243164,0.182292
// gj changed
visible=0
always_visible=0
zorder=99
background_color=0,0,0
ident=15652
gauge00=rxpGTN!GTN_650_2, 0, 0,100,100


[Window04]
file_1024=START_INSTRUCTIONS.bmp
size_mm=800,800
window_size=0.45
position=3
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident = 802

[Window05]
file_1024=DOOR_INSTRUCTIONS.bmp
size_mm=800,800
window_size=0.45
position=3
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident = 805

[Window06]
size_mm=800,800
window_size=0.45
position=3
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident = 801

gauge00=PAYLOAD_MANAGER!PAYLOAD,        0,0,800,800

[Window07]
ident = 71
visible = 0
sizeable = 1
size_mm = 419,381
position = 0
window_size = 0.343511450381679,0.556719107690809
window_pos = 0,0
gauge00 = MV_WX!WX2D,0,0,419,381,1
gauge01 = MV_WX!WX,64,121,291,205,1
gauge02 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

[Vcockpit01]
Background_color=0,0,0 
size_mm=900,900
visible=1
pixel_size=900,900
texture=$gps_1

gauge00=Learjet_35A!SYSTEM,             0,0,2,2
gauge01=Learjet_35A!FUEL_USED,          0,0,2,2
gauge02=Learjet_35A!FUEL_SYS,           0,0,2,2
gauge03=Learjet_35A!CLICK,              0,0,2,2
gauge04=Learjet_35A!SOUNDS,             0,0,2,2
gauge05=Learjet_35A!ALERTS,             0,0,2,2
gauge06=Learjet_35A!AP_MODES,           0,0,2,2
gauge07=Learjet_35A!SPD_HOLD,           0,0,2,2
gauge08=Learjet_35A!ALT_HOLD,           0,0,2,2
gauge09=Learjet_35A!VS_HOLD,            0,0,2,2
gauge10=Flysimware_Lear35A_Fuel_Dump_x64!Fuel_Dump,    0,0,2,2
gauge11=FBGS_XMLSound_x64!FBGS_XMLSound, 0,0,1,1,Sound\MT#97
gauge12=Learjet_35A!KEYS,               0,0,2,2
gauge13=FLYSIMWARE_CONSOLE!Navigation_REALITY650_2, 0,0,2,2
gauge14=dsd_p3d_xml_config_x64!config,  5,5,5,5, ./gauges/dsd_L35_xml_config_x64.ini
gauge15=dsd_p3d_xml_sound_x64!Sound,  2,2,2,2,./gauges/dsd_L35_xml_sound_x64.ini
gauge16=Learjet_35A!ANNUNCIATOR,     0,0,2,2

[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=512,512
texture=$VCRain

gauge00=FLYSIMWAREVCRAIN!VCRAIN,         0,0,512,512


[Vcockpit04]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$DME_1

gauge00=FLYSIMWARE35ADME!DME,         0,0,256,256

[Vcockpit05]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$DME_2

gauge00=FLYSIMWARE35ADME!DME1,         0,0,256,256


[Vcockpit06]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_1

gauge00=FLYSIMWAREHSI!HSI1,         0,0,256,256

[Vcockpit07]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_2

gauge00=FLYSIMWAREHSI!HSI2,         0,0,256,256


[Vcockpit08]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ALT_1

gauge00=FLYSIMWAREALT!ALT_LCD1,         0,0,256,256

[Vcockpit11]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$CLOCK_1

gauge00=FLYSIMWARE_DIGITAL_CLOCK!clock_oat,         0,0,1024,1024

[Vcockpit12]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$CLOCK_2

gauge00=FLYSIMWARE_DIGITAL_CLOCK!clock_oat2,         0,0,1024,1024

[Vcockpit13]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ATC_ID

gauge00=FLYSIMWARE_ATC_ID!ID_1,         0,0,256,256

[Vcockpit14]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ATC_ID2

gauge00=FLYSIMWARE_ATC_ID!ID_2,         0,0,256,256

[Vcockpit17]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADF

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio ADF1,         0,0,256,150


[Vcockpit18]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$NAV_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio NAV2,         0,0,256,150

[Vcockpit19]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$COM_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio COM2,         0,0,256,150

[Vcockpit20]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADF_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio ADF2,         0,0,256,150


[Vcockpit21]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Gauges0_PANEL

gauge00=FLYSIMWARE_DIMMER!Gauges0_PANEL,         0,0,1024,1024

[Vcockpit22]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Gauges1_PANEL
gauge00=FLYSIMWARE_DIMMER!Gauges1_PANEL,         0,0,1024,1024

[Vcockpit23]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Gauges2_PANEL
gauge00=FLYSIMWARE_DIMMER!Gauges2_PANEL,         0,0,1024,1024

[Vcockpit24]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Gauges3_PANEL
gauge00=FLYSIMWARE_DIMMER!Gauges3_PANEL,         0,0,1024,1024

[Vcockpit25]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$RADIOS_FLOOD

gauge00=FLYSIMWARE_DIMMER!RADIOS_FLOOD,         0,0,1024,1024

[Vcockpit26]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$RADIOS_EL

gauge00=FLYSIMWARE_DIMMER!RADIOS_EL,         0,0,1024,1024

[Vcockpit27]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$RADIOS_PANEL

gauge00=FLYSIMWARE_DIMMER!RADIOS_PANEL,         0,0,1024,1024

[Vcockpit28]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$PANEL1_FLOOD

gauge00=FLYSIMWARE_DIMMER!PANEL_1_FLOOD,         0,0,1024,1024

[Vcockpit29]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$PANEL5_EL

gauge00=FLYSIMWARE_DIMMER!PANEL_5_EL,         0,0,1024,1024

[Vcockpit30]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$PANEL2_EL

gauge00=FLYSIMWARE_DIMMER!PANEL_2_EL,         0,0,1024,1024

[Vcockpit31]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$PANEL3_EL

gauge00=FLYSIMWARE_DIMMER!PANEL_3_EL,         0,0,1024,1024

[Vcockpit32]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$PANEL4_EL

gauge00=FLYSIMWARE_DIMMER!PANEL_4_EL,         0,0,1024,1024

[Vcockpit33]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$COMPASS

gauge00=FLYSIMWARE_DIMMER!COMPASS,         0,0,1024,1024

[Vcockpit34]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$INTERIOR_MAP

gauge00=FLYSIMWARE_DIMMER!INTERIOR_MAP,         0,0,1024,1024


[Vcockpit35]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$INTERIOR_EL

gauge00=FLYSIMWARE_DIMMER!INTERIOR_EL,         0,0,1024,1024


[Vcockpit36]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ALTSET_LCD

gauge00=FLYSIMWARE_DIGITAL_ALTSET!ALTSET,         0,0,256,256


[VCockpit37]
size_mm=1024,1024
pixel_size=1024,1024
visible=0
texture=$GTN750RXP
background_color=0,0,0

gauge00=rxpGTN!GTN_750_1,  0,0,677,794

[VCockpit38]
size_mm=1024,1024
pixel_size=1024,1024
texture=$XPGTN650_2
background_color=0,0,0

gauge00=rxpGTN!GTN_650_2,  0,0,677,297

[Vcockpit39]
Background_color = 0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$MV_WXM
gauge00=MV_WX!WX,  0,0,512,361
gauge01 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143


Day=255,255,255
Night=255,255,55
Luminous=201,64,64



spacer.png

 

Edited by ark

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

3 hours ago, bofhlusr said:

Just the black screen for the whole monitor.

Are you running Win10 or Win11?

It could be the old install was never completely uninstalled. If it were me, I'd try this:

1.Using the Win Control Panel, I'd uninstall the Lear.

2. I'd then go to the location where the Lear was previously installed and make sure NO files or folders remained, and would delete any I found.

3. I'd then reinstall the Lear into that location, start the sim and see if the Lear loads. Since I had not run the Lear's GPS Management Tool, the installed GPS should just be the default GNS530, none of the RXP units should be in the plane at that point.

Note that after a fresh, clean install, you would have to run the Lear's GPS Management Tool in order to install the RXP GTNs.

 

Al

 

Edited by ark

  • Author
52 minutes ago, ark said:

Are you running Win10 or Win11?

If it were me, I'd try this:

1.Using the Win Control Panel, I'd uninstall the Lear.

2. I'd then go to the location where the Lear was previously installed and make sure no files or folders remained, and would delete any I found.

3. I'd then reinstall the Lear into that location, start the sim and see if the Lear loads. Since I had not run the Lear's GPS Management Tool, the installed GPS should just be the default GNS530, not any of the RXP units at that point.

Al

 

I did a bunch of tests.

I'm running Win10 Pro. 

From the Win Control Panel I uninstalled both Lear and Falcon.
I went to the ../simobjects/airplanes folder and deleted both Lear and Falcon folders
Did a cold (shutdown) boot.
Re-installed both planes from recently downloaded files. Noted that:
-- unlike the old installers the new installers no longer instruct to copy serial numbers to the Windows Clipboard
-- the install file for the Lear is called FLYSIMWARE_LEARJET_35A_V4.4.exe 
-- however, it installs version 4.3c of the Lear
===>The Lear had the same "MV_WX.DLL is locked" error. But, after 2-3 seconds it disappeared and the Lear ran with default avionics.

I rebooted P3D. Default vehicle is the default F-35.
This time I selected the Falcon.
Got the same dark screen error. Pressing Esc resulted in a CTD.
Rebooted P3D.

This time I selected the Lear again.
Got the same dark screen error.
Again, the only way to exit P3D is by pressing the Esc key, selecting a New Scenario which resulted in a CTD.
Rebooted P3D.

Selected the Falcon again.
Got the same dark screen error.
The only way to exit P3D is by pressing the Esc key, selecting a New Scenario which resulted in a CTD.
Rebooted P3D.

This time I selected the Lear again.
Got the same dark screen error. But only 1-2 seconds.
===> The Lear ran with default avionics. Apparently ok.
Rebooted P3D.

I selected the Falcon again.
Got the same dark screen error.
The only way to exit P3D is by pressing the Esc key, selecting a New Scenario which resulted in a CTD.

I must have rebooted P3D 10x doing various test scenarios each time using the default F35 as the default plane,and got the results above.

There is an MV_WX error in both Flysimware planes.
In the Lear, at least I can get to it but with default avionics (I'll test and use Flysimware's GPS Management tool next and hopefully get the RXP and WX avionics working in the Lear).
It's just so odd that right after the new installation, the Lear would get the same dark screen error, but would work at subsequent reboots of P3D.
Also odd, is that the Falcon won't run at all.

Hoping for  additional suggestions to fix the errors.  Any chance you can uninstall your Flysimware planes and re-install from the new installers to see if you get the same error? Thank you.

spacer.png

 

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

1 hour ago, bofhlusr said:

Any chance you can uninstall your Flysimware planes and re-install from the new installers to see if you get the same error? Thank you.

I did try a download and reinstall of the Falcon50 and had no problems -- all worked. And at this time I have not seen any other problem reports similar to yours.

The version issue, 4.4 vs 4.3c is just a typo in the installer text I think. You can check the version in the planes listing under Control Panel > Programs and Features.

Let's see if we can determine if the WX radar is causing a problem, or is just the victim of some other issue. So I suggest the below experiment. I'm using the falcon50 panel.cfg file below as an example, but you can do the same type of thing with the Lear if your prefer.

Comment out all references to the WX radar in the panel.cfg file, and back up the MV_WX.dll file in the gauges folder as shown below to disable it. Then restart the sim and see if the plane loads and works OK. If so, then the WX radar would seem to be the problem for some reason.However, if the problems persist, then I don't think the WX radar is at fault.

 

[Window Titles]
...
//Window05 = WX Advantage Radar
...

//[Window05]
//ident = 71
//visible = 0
//sizeable = 1
//size_mm = 419,381
//position = 0
//window_size = 0.343511450381679,0.556719107690809
//window_pos = 0,0
//gauge00 = MV_WX!WX2D,0,0,419,381,1
//gauge01 = MV_WX!WX,64,121,291,205,1
//gauge02 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

.....

//[Vcockpit30]
//Background_color = 0,0,0
//size_mm=512,512
//visible=0
//pixel_size=512,512
//texture=$MV_WXM
//gauge00=MV_WX!WX,  0,0,512,361
 

Also, rename the MV_WX.dll file in the gauges folder to something like MV_WX_BkUp.dll to back it up and disable it.

Edited by ark

  • Author

Excellent suggestion. I did as you suggested. Both planes are now working with the default avionics. Thank you.

Do you have a purchased version of the WX file?  If you have it, what is the date and the size of the file?

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Author

I just did another test. This time I renamed the MV_WX.DLL file in the gauges folder back to its original file name. MV_WX.DLL.

I uncommented the MV_WX entries in the panel.cfg files for both planes.

The result:
I still get the "MV_WX.DLL file is locked" error. But this time after a second or two, both planes would run with the default avionics.

I am recalling old issues with the MV_WX.DLL file. It seems problematic. I think we might even have exchanged posts in old messages threads about other issues with the file in the past. I am also wondering why the WX app is no longer being sold. 

--------
Edit:
I searched the forums and found this message thread regarding the Weather Advantage program.
Milviz Weather Advantage Radar stopped working - Dassault Falcon 50 - The AVSIM Community

It seems that the next troubleshooting step is to re-install and test the latest version of the Weather Advantage program. But where can I download the latest version?

Edit2:
I just relaunched P3D and ran Milviz 310.  The WX program runs perfectly. No "MV_WX.DLL is locked" error. For some reason the error only happens with Flysimware planes.

Edited by bofhlusr

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

1 hour ago, bofhlusr said:

Do you have a purchased version of the WX file?  If you have it, what is the date and the size of the file?

This is the entry I have in my P3Dv4 gauges folder.
spacer.png

Each time P3D was updated, the WX radar had to be updated as well. Initially REX did it, I think, then they turned it over to Milviz to maintain. Finally, as I understand it, when one of the P3Dv5 updates came along, Milviz decided the cost and difficultly that would be required to update the WX radar vs sales potential made it no longer a viable product.

I see I have a MV_WX.dll file in my P3Dv5 gauges folder which I had renamed because it no longer worked. The size of that file is 3739KB and the entry date is 8/26/2020.

I also see I have a MV_WXM.dll file in my P3Dv4 modules folder (3113KB, 4/21/2020).  REX support, in response to a question about there being two Milviz WX radar dll files, said:

Yes, the one in the modules folder (Program Sim Compatibility) allows the WX Radar to work with the Sim version and the one in gauges folder is the actual WX Radar...(for the aircraft). 

So it seems you should have two Milviz WX radar dll files.

 

 

Edited by ark

  • Author

Problem solved.

The date of your MV_WX.DLL file is later than mine (which is 3/22/2018), AND, that is the culprit in the issue I was having. How I got that old dated file I'd probably never know since I was able to retrieve a file with the same date as yours from one of my disk image backups. I'm just glad I have these two Flysimware planes working again. I'll do some more test to make sure I have fully functional copies before doing a disk image again.

I checked my ../modules folder.  I don't have an MV_WXM.dll file there. Does your P3Dv4.5 still work if you temporarily delete the MV_WXM.dll file from your modules folder?  
 

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Author
1 minute ago, ark said:

Is your P3Dv4, the Lear, and the Falcon all on the same drive?

Yes. They are both installed in C:\P3D which is on an NVMe drive with about 1TB of free disk space.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.