• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX:SE Size of VC gauges causing CTD when switching between VC and 2d panel?

B

BlueSox14

Messages
45
Country
australia
Hi all,

I have been working on a project to adapt G Munro's freeware 747 panel (with his permission) to the default FSX:SE 747-400 VC.

I have created an xml gauge for each of the 6x CRT screens (so 6x .xml gauges) and mapped them to a new and third $747_3 VC texture (1024x1024) in the panel.cfg. All working really well when in the VC.

I discovered that when switching views between the VC and the 2D panel, I was freezing the sim, effectively a CTD because as soon as I hit alt + enter, the application disappears.

After some investigation I discovered that if I comment out one of the 6x gauges in the panel.cfg (it doesn't seem to matter which one - effectively causing one of the screens to go blank in the VC) then the problem of switching between the VC and 2D panel disappears.

Can anyone explain what might be occurring here?

1) Have I tipped over some gauge size memory limit constraint within FSX?
2) If so, where is the constraint? Is it the total size of all gauges used by the aircraft? Total size of gauges used in the VC? In the compiled model?

The total size of the 6x xml gauges mapped to the $747_3 texture is 1.83Mb. There are 2x other $747 textures also being used (effectively the default ones).

For what it's worth, to facilitate screen switching within the VC, the below pieces of code are assigned to each screen (and controlled by visibility variables):

Screen 1 PFD only
Screen 2 Navigation Display, PFD & Secondary EICAS
Screen 3 Primary & Secondary EICAS
Screen 4 Navigation Display, PFD & Secondary EICAS
Screen 5 PFD only
Screen 6 Primary & Secondary EICAS

I've never had a problem before with the above method for facilitating screen switching, but could the crash be caused by conflicting code/variables? I feel this is unlikely because the gauges work just fine within the VC and trial flights. Just putting the idea out there for what it's worth.

Thanks everyone.

Trent
 
I can't speak for XML, but I know from experimenting in C that FSX will take gauges up to a siz of a little over 512,000 bytes (about 490Mb), so that's not likely to be the problem.
 
something similar to GPS map that use in several gauge (4), it not get CTD, but if got 1-2 FPS.
so decide to use 1 gauge for all. with same logical (my :twocents: ), disable 3D gauge when 2D gauge in use, vice versa.
 
You must log in or register to reply here.
Back
Top