• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

2D panels cause CFS2 to freeze

Windows 7,8 or 10?

Open the panel.cfg with Wordpad or Notepad and remove all

render_3d_window=1

fround in the panel.cfg.

The basic of why CFS2 will lockup Windows 7,8 or 10 is that CFS2 and Windows 7,8 or 10 don't like have panel .bmps that are only 1024x768.
 
Thanks ALlen,

I'm running Windows 7 currently. What exactly does "render_3d_window=1" do, and why does Windows 7,8, and 10 dis like .bmps that are only 1024X768? Is there a way I can resize the .bmp files?

Thanks!
Browncoat
 
"render_3d_window=1" locks the bitmap in place. Panels with "render_3d_window=0" or no "render_3d_window=" the bitmap can be click on and dragged around on the screen like popup throttle or nav panels.

Why does Windows 7,8, and 10 dis like .bmps that are only 1024X768 is unknown. Basic MS paint should be able to resize them down to 800x600 but some system are having probs with render_3d_window= even with 800x600 and 640x480 panels .bmps. The best thing to do is remove "render_3d_window=1" and call it good.
 
...What exactly does "render_3d_window=1" ...

There are other benefits as well. If you do a lot of panel mods, you will note that all gauge switches fall into two main categories: CFS2-friendly and not. The friendly camp is subdivided between CFS/CFS2, FS98 and FS2000. If you have a panel setup as (=0), all of these types of switches and buttons are mouse clickable in 2D. But if the panel is (=1), only the CFS/CFS2 and FS2000 will be clickable - the older FS98 stuff is just static panel decor. So (=0) is a good way to go in most cases.

However, the downside of (=0) is your target box, display messages and "park brake" message will appear behind the 2D structures of the panel, cockpit window or canopy framing, whereas with (=1) all of these are visible on top of the 2D structures. In many of the legacy models we still fly today you will find some creative 2D panel setups designed to circumvent this quirk. For example, on some you might find a two part main panel with the canopy and windshield frame separate from the instrument panel itself. The upper framing will be (=1) in the pane.cfg, but the separate lower instrument area will be (=0) to keep the FS98 stuff clickable.
 
Oh... Forgot about those odd things... Haven't had to deal with them since the CFS1 days...
 
Back
Top