Question (Silly-dummy)

[nik112]

Hi guys,

I want to ask if we can add FS9 or FSX mesh to CFS2. Is it possible?

cheers

 

[bearcat241]

Nick, it seems you never got an answer on this, but it really is a good question. It is sometimes possible to use the mesh. Technically the answer is an indisputable yes in theory. But visually speaking, it depends on how well the level of detail at the shorelines matches up with the lines drawn in CFS2 - many times they don't and you'll be pressed to use coastal flattens to make the spots look right.

And then there's always the chance that some anomaly will appear in the middle of a body of water, like small water mountains or hills. These are spots that have some type of land mass in FSX and FS9, but not in the CFS2 terrain mapping, but the FSX mesh still does its job by reflecting the shape and height of the mass even though its painted as water and treated so by CFS2. You don't see these often but they do show up here and there, mostly in places that have a lot of small island groupings in the real world. Your biggest headache will come from the shoreline issues. But hey, inexpensive code in virtual world is full of such imperfections.

 

[nik112]

Nick, it seems you never got an answer on this, but it really is a good question. It is sometimes possible to use the mesh. Technically the answer is an indisputable yes in theory. But visually speaking, it depends on how well the level of detail at the shorelines matches up with the lines drawn in CFS2 - many times they don't and you'll be pressed to use coastal flattens to make the spots look right.

And then there's always the chance that some anomaly will appear in the middle of a body of water, like small water mountains or hills. These are spots that have some type of land mass in FSX and FS9, but not in the CFS2 terrain mapping, but the FSX mesh still does its job by reflecting the shape and height of the mass even though its painted as water and treated so by CFS2. You don't see these often but they do show up here and there, mostly in places that have a lot of small island groupings in the real world. Your biggest headache will come from the shoreline issues. But hey, inexpensive code in virtual world is full of such imperfections.

Thanks DJ for you reply. Your answers are always hitting the target.
Βtw i want to ask you for a strange phenomenon that i had last night. Tried to flew a mission and when i pressed the "fly now" button the game freeze. Then i pressed esc and exit. i opened cfs2.cfg and at situational options all were "0". i change them to "1".
[ i had made the quest about 10-15 days ago here and the answers that i got was to check panel-sound- air-dp]. My conclusion about this is the panel.
if i replace the panel folder with stock f6f3 the game runs smoothly. The only plane that flies at any time its the fdg2 p51. For the rest i use stock panels-f6f3,f4f4,p38 even for axis planes such us me109 fw190.
If you have something in mind please share.

cheers

 

[bearcat241]

Nick,

If you think you've narrowed the problems down to panel issues, it may be caused by legacy FS gauges and possibly some newer ones that are supposed to have CFS2 compatibility. This same type of problem is common in the FS series also. The FS community came up with a solution some time ago that seems to work well against the gauges problem in CFS2 as well. Copy and paste the text below anywhere in your CFS2.cfg file:

[OldModules]
FSSound.dll=1
GaugeSound.dll=1
cfo_weather.dll=1

[OldGauges]
00.DC3-TGL30.ca.gau=1
00.DC3-TGL31.ca.gau=1
00.DC3-TGL34.ca.gau=1
CFR1_fpda_dummy_switch_1.gau=1
zSperry.markiii.gau=1
Sperry.markiii.gau=1
Sperry.markiii.fo.gau=1
Sperry.markiiifo.gau=1
rww2-Sperry.markiii=1

Any time you encounter a suspicious gauge or a dll module (residing in the MODULES folder) that you think may be a problem, add its name to one of the groups above, according to its file type. I don't have the technical explanation for how or why this works, except that it basically commands the sim to stop bitching about the file in question and just get on with the show...LOL

Hope this helps...

 

[nik112]

hi dj
i tried it but no luck, same results.

cheers

 

[bearcat241]

First, are you running XP, Vista, Win7 or Win8? Secondly, is the system 32 bit or 64 bit? Lastly, post the full text of one of the panel.cfg's giving you trouble for an example.

 

[Blood_Hawk23]

here is something that i had to do with my current computer.

but first, what size is the panel texture?

I had to reduce some of the FoxFour panels to 800x600. after i did that i had no more trouble. the final fix came when i updated all of my video drivers and added silverlight. i don't no why it worked but it did.

 

[bearcat241]

That seems to be a common fix for this problem in CFS2 operating in Win7x86 and x64 only. It doesn't apply to XP, because CFS2 handles larger panel textures with no probs in this platform. This is why i'm asking for more details.

 

[Allen]

Any time that a aircraft only has a panel that is 1024x786 it will lock up on Win7 as soon as the 2d panel is displayed. (This may apply to Win 8)

The quickest thing to do is to pixel resize down to 800x600.


bearcat241

CFS2 on Win7 will work with large panels but as long as it is set up right. Most of older addons have the panel.cfg set up like this
[Window00]
file=Panel_Background.BMP (Is 1024x768)
position=4
size_mm=640,480
window_pos=0.0,0.0
window_size=1.000,1.000
render_3d_window=1
sizeable=1
visible=1
ident=MAIN_PANEL

As above won't work on Win7. For Win7 to use 1024x786 you need it to look like this
[Window00]file=Panel_Background_640.BMP (Is 640x480)
file_1024=Panel_Background_1024.BMP (Is 1024x768)
position=4
size_mm=640,480
window_pos=0.0,0.0
window_size=1.000,1.000
render_3d_window=1
sizeable=1
visible=1
ident=MAIN_PANEL

The above is from any of the stock aircraft panel.cfg and the works on Win7 using the larger 1024x768. Every aircraft I've updated or made I made sure to fix the panel so that it uses a 640x480 and 1024x786 panel.This makes them have a Win7 safe panel.

 

[bearcat241]

This is all interesting stuff Allen and Blood Hawk, but until the man replies with the details how do we know if any of this applies to his problem.

But to clear things up a bit Allen, let me point out something in your post.

CFS2 on Win7 will work with large panels but as long as it is set up right. Most of older addons have the panel.cfg set up like this

[Window00]
file=Panel_Background.BMP (Is 1024x768)
position=4
size_mm=640,480
window_pos=0.0,0.0
window_size=1.000,1.000
render_3d_window=1
sizeable=1
visible=1
ident=MAIN_PANEL

As above won't work on Win7. For Win7 to use 1024x786 you need it to look like this

[Window00]
file=Panel_Background_640.BMP (Is 640x480)
file_1024=Panel_Background_1024.BMP (Is 1024x768)
position=4
size_mm=640,480
window_pos=0.0,0.0
window_size=1.000,1.000
render_3d_window=1
sizeable=1
visible=1
ident=MAIN_PANEL

The size that the sim is applying to the bmp is determined by this line in the cfg: size_mm=640,480. The actual file size is irrelevant. This command line in the cfg forces the sim "convert" the size on the fly and present it in 640x480 micrometers (pixels) no matter what. This is where Win7 stumbles and hangs, during this conversion process. For whatever reasons, the OS interferes with the conversion and halts the process with a program fault. However, it seems OK with converting 800x600 to 640x480. Your options are to either change the file size to 800x600 or 640x480 or simply change this line in the cfg to size_mm=1024. If you choose to change this line, the sim will apply the original 1024 bmp with little stress. But if you choose to change the file size, you don't need both these lines:

file=Panel_Background_640.BMP
file_1024=Panel_Background_1024.BMP


The first line will be enough:

file=Panel_Background_640.BMP

And again, all of this may be pointless if Nick is running XP. In that case the problem is elsewhere.

 

[nik112]

Hi dj
i run win7*64 and that's the panel cfg--Morton's fw190-a

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Wednesday, June 07, 2006 at 22:28 FSPS Build:15838

[Window Titles]
Window00=Main
Window01=sticks
Window02=Radio
Window03=GPS
Window04=Electric
Window05=Fuel Selector


[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,05,RADIO_STACK_PANEL,GPS_PANEL,125,overhead_panel

VIEW_FORWARD_ZOOM=0.750
VIEW_FORWARD_DIR=1.700, 0.000, 0.000

VIEW_FORWARD_RIGHT_ZOOM=0.750

VIEW_RIGHT_ZOOM=0.750

VIEW_REAR_RIGHT_ZOOM=0.750

VIEW_REAR_ZOOM=0.750

VIEW_REAR_LEFT_ZOOM=0.750

VIEW_LEFT_ZOOM=0.750

VIEW_FORWARD_LEFT_ZOOM=0.750

VIEW_UP_ZOOM=0.750

VIEW_DOWN_ZOOM=0.750



//--------------------------------------------------------
[Window00]
file_1024=mk_fw190a.bmp
size_mm=640,480
window_size_ratio=1.000
position=4
visible=1
ident=MAIN_PANEL
sizeable=1
render_3d_window=1
image_blend= 1.000
window_size= 1.000, 1.000
window_pos= 0.000, 0.000

gauge00=fsd_fw190.airspeed, 185,320,40,40
gauge01=fsd_fw190.fuel, 315,386,23,22
gauge02=fsd_fw190.fuel.low, 308,415,9,7
gauge03=fsd_he111.adi, 228,309,57,58
gauge04=fsd_he111.rpm.1, 394,362,39,39
gauge05=fsd_he111.oiltemp.1, 258,384,24,24
gauge06=fsd_he111.boost.1, 374,322,38,38
gauge07=fsd_he111.flapind, 340,385,24,23
gauge08=fsd_he111.radtemp.1, 233,384,23,24
gauge09=komet.alt, 162,358,40,43
gauge10=komet.vsi, 288,321,40,42
gauge11=fsd.he111.gyro, 332,323,39,37


//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=800,600
window_size_ratio=1.000
position=4
visible=1
ident=05
sizeable=1
render_3d_window=1
window_size= 0.640, 0.230
window_pos= 0.000, 0.780

gauge00=P40 Stickhand, 481,237,249,543


//--------------------------------------------------------
[Window02]
file=nav-bg.bmp
file_1024=nav-bg.bmp
size_mm=313,480
position=2
visible=0
ident=RADIO_STACK_PANEL

gauge00=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 54,1,208,78
gauge01=Bendix_King_Radio!Bendix-King Radio ADF, 55,82,208,55
gauge02=Bendix_King_Radio!Bendix-King Radio DME, 54,141,208,54
gauge03=Bendix_King_Radio!Bendix-King Radio AP, 52,198,208,64
gauge04=Bendix_King_Radio!Bendix-King Radio Xpndr, 54,270,208,64
gauge05=BENDIX_KING.ADF.SLAVED, 20,350,98,97
gauge06=Alpha_HSI, 196,341,101,113
gauge07=extra-300!Nav GPS Switch, 134,372,37,52


//--------------------------------------------------------
[Window03]
Background_color=0,0,0
size_mm=456,378
window_size_ratio=1.000
position=8
visible=0
ident=GPS_PANEL
window_size= 0.360, 0.370
window_pos= 0.000, 0.070

gauge00=gps!gps, 12,1,300,372


//--------------------------------------------------------
[Window04]
file=electric.bmp
size_mm=130,295
position=2
visible=0
ident=125

gauge00=fsd_generic.landing_lights, 71,213,21,22
gauge01=fsd_generic.pitot, 71,79,21,22
gauge02=extra-300!Avionics Switch, 74,128,21,22
gauge03=extra-300!Boost-Pump-Switch, 72,55,21,22
gauge04=extra-300!Alternator-Switch, 73,26,20,22
gauge05=extra-300!Interior-Light-Switch, 71,240,21,22
gauge06=extra-300!Master-Switch, 75,106,21,22
gauge07=extra-300!Nav GPS Switch, 73,183,20,30
gauge08=extra-300!Strobe-Light-Switch, 73,156,21,22


//--------------------------------------------------------
[Window05]
file=fuel.bmp
size_mm=130,340
position=3
visible=0
ident=overhead_panel

gauge00=fw190a!Fuel_Selector, 16,51,29,198


//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$panel1

gauge00=fsd_fw190.airspeed, 6,1,94,98
gauge01=komet.alt, 104,3,94,103
gauge02=komet.vsi, 309,104,98,104
gauge03=fsd_he111.adi, 206,3,97,98
gauge04=fsd_he111.boost.1, 101,209,89,88
gauge05=fsd_he111.flapind, 107,310,82,83
gauge06=fsd_he111.gearind, 314,331,89,45
gauge07=fsd_he111.oiltemp.1, 207,209,83,83
gauge08=fsd_he111.proppitch.1, 310,207,96,95
gauge09=fsd_he111.radtemp.1, 12,313,84,83
gauge10=fsd_he111.rpm.1, 101,105,94,97
gauge11=fsd_fw190.fuel.low, 423,62,29,30
gauge12=fsd_fw190.fuel.low, 472,10,30,31
gauge13=fw190a!Clock, 424,218,78,75
gauge14=fw190a!Fuel_Selector, 426, 337 ,42,112
gauge15=GerWW2_flaps, 36,408,84,86
gauge16=gerww2_stall_lamp_0001, 425,14,28,30
gauge17=fsd.he111.gyro, 316,10,85,84
gauge18=fsd_fw190.fuel, 207,311,83,80
gauge19=fsd_he111.boost.1, 207,108,91,91



[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6033

cheers

 

[Blood_Hawk23]

actually i have windows XP sp3. it wasn't until i did the update that the problem went away. I'm not disagreeing with anyone. and only throwing out the issue i had.

 

[Allen]

This is all interesting stuff Allen and Blood Hawk, but until the man replies with the details how do we know if any of this applies to his problem.

But to clear things up a bit Allen, let me point out something in your post.


The size that the sim is applying to the bmp is determined by this line in the cfg: size_mm=640,480. The actual file size is irrelevant. This command line in the cfg forces the sim "convert" the size on the fly and present it in 640x480 micrometers (pixels) no matter what. This is where Win7 stumbles and hangs, during this conversion process. For whatever reasons, the OS interferes with the conversion and halts the process with a program fault. However, it seems OK with converting 800x600 to 640x480. Your options are to either change the file size to 800x600 or 640x480 or simply change this line in the cfg to size_mm=1024. If you choose to change this line, the sim will apply the original 1024 bmp with little stress. But if you choose to change the file size, you don't need both these lines:

file=Panel_Background_640.BMP
file_1024=Panel_Background_1024.BMP


The first line will be enough:

file=Panel_Background_640.BMP

And again, all of this may be pointless if Nick is running XP. In that case the problem is elsewhere.

Even aircraft that are using size_mm=640,480 (stock aircraft) will use the 1024x786 panel in full screen mode if screen res is 1024x786. Also removing render_3d_window=1 will let the panel work fine in Win7

 

[bearcat241]

Nick,

I've attempted to duplicate your problem as best i could. I installed this same panel configuration into my MZ_FW190A unmodified and ran it in Win7 x64. I experienced no problems worth noting, except that Window02 calls for a nav-bg.bmp which is not included in Morton's FW190 panel package, so you get the gauges without a background in that window. Nothing serious about that. Also, Window03 doesn't show at all because the single GPS gauge is an FS2002/FS2004 gauge that isn't compatible with CFS2, so that's to be expected and can be easily fixed. Its the only gauge in the entire panel that's not CFS2 compatible, but it will not hang your program - it just fails to appear no what OS you use. The render_3d_window=1 setting has no adverse effect either.

Also worth noting, the VC section in this cfg isn't usable in the MZ model, but i also expected that when i chose to try the panel without any mods. But i mention this to say this didn't prevent the program from loading the model.

If this is your worst example in terms of freezing your program, i think the source of your problem may be related to your global system graphics settings and/or hardware as they relate to CFS2 and not specifically the add-on panels themselves. Because graphics settings and hardware can differ so widely between individual users, this may be a difficult area to assist you with in a forum and may require a more physical, hands-on approach by someone closer to home.

Although i run CFS2 in both XP sp3 (x86) and Win7 (x64), i prefer using it in XP for the sake of simplicity. This sim is one of the principal reasons that i dual boot my computer with both systems. Win7 x64 has these random, underlying issues with CFS2's 32 bit code that even compatibility mode can't fix and then there's the security related stuff you have to deal with. You have to do a lot more tweaking to get things running smoothly and KEEP them in line.

Do you have any other examples?

 

[Blood_Hawk23]

I think your right. it sounds like a graphics issue.

have you updated your drivers?

is there any other panel giving you trouble? maybe we can narrow it down.

 

[nik112]

Hi guys
Another panel cfg ( p-51d-Araks)

// Panel Configuration file
// This Panel.cfg file created by Araks


[Window Titles]
Window00=%window_title_00%
Window01=%window_title_01%
window02=%window_title_03%

[Window00]
file=P-51d_CC.bmp
size_mm=640,480
window_pos=0.0,0.0
window_size=1.000,1.000
render_3d_window=1
position=7
sizeable=1
visible=1
ident=0

gauge00=P51d!Airspeed,167,356,60
gauge01=P51d!Altimeter,166,420,56
gauge02=p51D!Attitude,290,346,70
gauge03=P51d!Boost_Pressure,357,420,60
gauge04=P51d!Clock,408,302,44
gauge05=P51d!Engine_Temperature,365,322,44
//gauge06=P51d!Flaps,126,422,28
gauge06=P38F_Lightning!Fuel-Selector,123,432,30
gauge07=P51d!Fuel,365,373,44
gauge08=P51dX!Fuel_Selector,523,441
gauge09=P51d!Gear,422,466,42
gauge10=P51d!Heading_Indicator,232,352,54
gauge11=P51dX!Magneto,88,411
gauge12=P51d!Oil_Pressure,420,409,56
gauge13=P51d!Starter,394,290,12
gauge14=P51d!Tachometer,410,348,60
gauge15=P51d!Turn_Indicator,226,420,60,58
gauge16=P51d!Vertical_Speed,290,420,60,58
gauge17=p38f_lightning!Magnetic-Compass,194,292,55

[Window02]
file=K-14A.bmp
size_mm=640,480
window_size_ratio=1.0
position=7
visible=1
ident=50


[Window01]
file=
position=6
size_mm=640,80
window_size_ratio=1.0
position=7
sizeable=1
visible=0
ident=70

gauge00=P51d!thrust_controls,56,16,48,64
gauge01=P51d!Fuel_Selector,510,44,40
gauge02=P47d!Magneto,550,42,40

[VCockpit01]
Background_color=0,0,0
position=7
size_mm=512,512
pixel_size=512,512
texture=$P51D-L
visible=0
ident=

gauge00=p38f_lightning!Magnetic-Compass,153,0,120
gauge01=P51d!Airspeed,97,137,120
gauge02=P51d!Heading_Indicator,227,137,120
gauge03=P51d!Attitude,357,137,140,FORCE_TRANS
gauge04=P51d!Altimeter,97,277,120
gauge05=P51d!Turn_Indicator,227,277,120
gauge06=P51d!Vertical_Speed,357,277,120
gauge08=P51d!Gear,370,420,117

[VCockpit02]
Background_color=0,0,0
position=7
size_mm=512,512
pixel_size=512,512
texture=$P51D-R
visible=0
ident=

gauge00=P51d!Starter,165,0,30
gauge01=P51d!Clock,220,0,90
gauge02=P51d!Engine_Temperature,150,75,90
gauge03=P51d!Tachometer,240,110,130
gauge04=P51d!Fuel,150,175,90
gauge05=P51d!Boost_Pressure,135,277,120
gauge06=P51d!Oil_Pressure,258,255,120
//gauge07=P51d!Magneto,300,100,80

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=5240

[Strings]
"window_title_00"=P40B -- Main Panel
"window_title_01"=P40B --Throttle gunsight


ps:as for updating my graphics driver i want to tell you that i have installed the latest nvidia drivers 310.... and another prob (visual) revealed, but i think to do another thread for this

cheers

 

[bearcat241]

Ouch!...this one's in bad shape. Is this your best copy of Arak's original? Well, whatever the case, i sent you my copy with mods. Check your email...

 

[nik112]

Thanks dj
i got it

cheers

 

[nik112]

Hi dj
i made an attempt last night and failed. i 'll try again tonight and i 'll inform you.

cheers