B-52 panel with VC

aeromed202

aeromed202

SOH-CM-2014
Just found a long over-due panel for this bomber at FlightSim by David Henry Company. Problem is it makes my FS9 crash. I let some of the gauges over-write and got some errors when loading anything that uses them. I copied originals back which fixed those problems but the panel alone still causes a game crash. I e-mailed the author to see what can be done. Can't wait to get this up and running.
 
That looks like the modern panel for the H-version, but the one i Have is not a BC, only a 2-D. Mind if you share a lonk?

On most occasions when one is presented with that error message, it is because it is an old module not recognized by FS9. In these cases one needs to pen their FS9.cfg and add this for Old Modules near the bottom:


[OldModules]
name of dll=1

Caz
 
Hi,

On most occasions when one is presented with that error message, it is because it is an old module not recognized by FS9. In these cases one needs to pen their FS9.cfg and add this for Old Modules near the bottom:
Click to expand...

You right (it's a basic :) )
But even when you have a error message with a old module DLL .. FS2004 don't crash :)
Here I have the real error window (restart FS2004 ?) and the culprit is "noname.dll" as you can have fe.dll .. weather.dll etc !
You load the B-52 with this panel .. the HD work for sometime .. FS2004 crash and window error message popup !
FS2004 had already crashed when this error window appear :)
 
Crash and error

Hi,

a32oi0.jpg


n4iagp.jpg


4huuyh.jpg


Panel used:

FS2004 (ACOF) - FS2004 Panels FS2004 USAF B-52 (G/H Models) Panel
[SIZE=-1][ Download | View ] [/SIZE]
Name: b52_panel.zip Size: 17,382,158 Date: 12-12-2009 Downloads: 714
b52_panel.gif
[SIZE=-1] FS2004 USAF B-52 (G/H Models) Panel. Accurate US Air Force Boeing B52 panel with EVS/FLIR monitor. It also includes standard flightsim controls (GPS, autopilot, etc.) for easier aircaft flying. Created by David Henry Company.[/SIZE]

Note:

714 downloads .. and maybe 714 FS2004 crashes :)
 
That's the one I have for my H. It works fine for me, but it is 2-D only. I get no error message. I would suggest a uninstall remove the old files and do a reinstall. I only use this panel for the H variant, I use the KM Panel for early variants.

Caz
 
Hi,

Fresh reinstall of the B-52 .. fresh reinstall of the panel.
No way :isadizzy:
So .. I continue to use the KM Panel with joy :icon_lol:
 
I am in contact with the maker so if I get any results I'll post 'em. I never got an error when I tried loading the panel, just that twittering activity light and buzzing noise that says "you ain't flyin right now, I chokin' on a peanut... be back in five".:blind:
 
claudius24 said:
Note:
714 downloads .. and maybe 714 FS2004 crashes :)
Click to expand...

Maybe just 713.
This panel works fine for me without any issues - right from the start. :engel016:

Dunno which gauges came with the panel (I'm at the office now with no access to FS), but maybe it's one of those nasty gaugesound.dll crashes?

Perhaps removing the "FLIR" window from the panel.cfg will do?

Cheers,
Markus.
 
Hmmm - back at the flight desk again, I took a quick look at the panel.cfg file:
With the exception of the dc_concorde.ins.server, I can't figure out which gauge may cause the problem - they are more or less standard gauges.
And the "FLIR window" I suspected in fact is just a - literally - black hole in the dashboard. D'uh!
 
I'm in a bit of a fix now. Seems all aircraft that use gauges connected with the default 747-400 cause an instant game crash when selected. All this started when I fired up the B-52 panel with VC. I didn't have a back-up of default gauges so I was wondering which disk those are on. I have a trial version of WinRAR to hopefully open them up and make a good back-up. Any help appreciated.
 
Well, the panel works fine for me in 2-D, and even though there is text for a VC in the Panel.cfg, I still have no VC.

Caz
 
The default gauge re-install worked insofar as I can now load heavies again, and like you Caz the new B-52 panel only comes up in 2d. But at least the crashes seem to be gone:applause:
I'll let the author know all this, he has been very interested in my problem. The only gauge error so far is RP733 that came up for a PROJECT AIRBUS A319 so I'll look into that.
 
Do you get the VC model but with no panel?

If so, post the vcockpit section (top section) of the panel.cfg and maybe we can help.
 
Milton,

here is the VCockpit section of the Panel.cfg. There is reference to a string texture, but no such texture can be found.

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$b52_panel_1

//gauge00=fsd_rf4.adi, 100,68,40
gauge01=737-400!HSI, 70,80,30
gauge02=Mooney_Bravo!OMI Lights, 90,50,5
gauge03=737-400!Clock, 50,112,15
gauge04=Lear_45!Backup Altimeter, 91,118,16
gauge05=737-400!Airspeed, 109,118,16
gauge06=Extra-300!Turn-Coordinator, 74,118,16
gauge07=Cessna!Heading_Indicator, 109,140,16
gauge08=Concorde!Airspeed, 91,140,16
gauge09=Concorde!Machmeter, 158,140,16
gauge10=737-400!Altimeter, 176,118,16
gauge11=737-400!Vertical Speed, 158,118,16
gauge12=Cessna!Attitude, 176,140,16
gauge13=Concorde!Temperature, 184,165,16
gauge14=737-400!Flaps, 205, 125 ,20
gauge15=Concorde!Control-Surfaces, 205,145,25
gauge16=Concorde!VOR, 230,125,25
gauge17=Concorde!ADF, 230,155,25


//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$b52_panel_2

//gauge00=fsd_rf4.adi, 116,68,40
gauge01=737-400!HSI, 157,80,30
gauge02=737-400!Clock, 165,118,15
gauge03=Lear_45!Backup Altimeter, 148,118,16
gauge04=737-400!Airspeed, 130,118,16
gauge05=737-400!Vertical Speed, 77,118,16
gauge06=737-400!Altimeter, 57,118,16
gauge07=737-400!Fuel Quantity, 0,125,40
gauge08=Concorde!Gear-Indicator, 10,155,15
gauge09=Concorde!Gear-Handle, 30,145,15


//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$b52_panel_3

gauge00=Concorde!Engine-N2, 8,110,30
gauge01=Concorde!Engine-N2, 38,110,30
gauge02=Concorde!Engine-N2, 68,110,30
gauge03=Concorde!Engine-N2, 98,110,30
gauge04=Concorde!Engine-N2, 128,110,30
gauge05=Concorde!Engine-N2, 158,110,30
gauge06=Concorde!Engine-N2, 188,110,30
gauge07=Concorde!Engine-N2, 218,110,30
gauge08=Concorde!Engine-N1, 8,140,30
gauge09=Concorde!Engine-N1, 38,140,30
gauge10=Concorde!Engine-N1, 68,140,30
gauge11=Concorde!Engine-N1, 98,140,30
gauge12=Concorde!Engine-N1, 128,140,30
gauge13=Concorde!Engine-N1, 158,140,30
gauge14=Concorde!Engine-N1, 188, 140 ,30
gauge15=Concorde!Engine-N1, 218,140,30
gauge16=Concorde!Fuel-Flow, 8,170,30
gauge17=Concorde!Fuel-Flow, 38,170,30
gauge18=Concorde!Fuel-Flow, 68,170,30
gauge19=Concorde!Fuel-Flow, 98,170,30
gauge20=Concorde!Fuel-Flow, 128,170,30
gauge21=Concorde!Fuel-Flow, 158,170,30
gauge22=Concorde!Fuel-Flow, 188,170,30
gauge23=Concorde!Fuel-Flow, 218,170,30
gauge24=Concorde!EGT, 8,200,30
gauge25=Concorde!EGT, 38,200,30
gauge26=Concorde!EGT, 68,200,30
gauge27=Concorde!EGT, 98,200,30
gauge28=Concorde!EGT, 128,200,30
gauge29=Concorde!EGT, 158,200,30
gauge30=Concorde!EGT, 188,200,30
gauge31=Concorde!EGT, 218,200,30
 
Hello Milton. I'm going back and forth with the author. His read-me says you can create a VC view within the monitor rectangle in the 2D view but I am finding out if it was intended to have a panel too.
 
You haven't stated if there is a VC model yet ... when scrolling through the views after the 2D view?

If so, based on the panel.cfg entries, there should be 3 textures in the texture folder for the 3 vcockpit sections.

b52_panel_1.bmp, b52_panel_2.bmp, b52_panel_3.bmp or some variant like vc01, vc02, vc03, unless the textures were baked on.

However, even if these textures were not there, the gauges should still be present on a blank vc panel model if the texture=$b52_panel_1 names are correct.

Of course, if you are not seeing a vc model at all, well ...
 
You must log in or register to reply here.
Back
Top