• 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.

FSXA Improving FPS question

delivery guy

delivery guy

Messages
1,749
Country
unitedstates
I noticed when you put too many codes in an interior model the FPS gets worse. External code does not seem to have much effect.
My question is i usually write my conditions for annunciator lights all in the hard coding. If i put a basic Lvar for each annunciator then write the condition in external code will the FPS improve?

I recently learned that Lvars would not flood in external coding even without anti flooding each Lvar. So knowing this now i want to start putting more Lvar coding in the external code rather than hard coding if the FPS will improve.

I have a lot of annunciator lights and other code i can put in external coding so we are not talking about just a few codes. I am looking to significantly improve the FPS without losing code.
 
Although I am not a modeller ( cant grasp gmax or max ) I do quite a bit a of coding for a few of them.
I like throwing code into logic gauges in the VC. Using the panel system to do all the work sending the final result to the visual model via single L:Var.
The upside? Instant changes can be done without recompiling.
Not really sure on the ramifications but i do believe that using the panel system is better as it is limited/throttled in the sim at 18hz max whereas anything in the visual model coding runs at the frame rate.
Just 2 cents worth..
 
Last edited:
In general, anything that's not framerate-critical should be put into external gauges. They're much easier to debug to boot.

I also don't know why annunciatiors need to be 3D objects. Drape a gauge polygon over them and let them be handled by the 2D panel logic. Again, they can be debugged much easier that way.
 
If there are a great deal of annunciators... using gauge polys to display them will cause a massive frame rate impact.
 
WarpD said:
If there are a great deal of annunciators... using gauge polys to display them will cause a massive frame rate impact.
Click to expand...

So your saying it might be better to make a 2D gauge that looks like 3D annunciator lights which would also be external logic.
I have noticed the model does not like it when you use too many poly vis tagged parts.

spokes2112
Yes we were talking about how 18hz would not effect the FPS that bad. So knowing the hard coding is updated based on the FPS is good to know.

Heretic
I always knew that external coding is faster to test code. Bill taught me that a long time ago. But never mentioned if you use too much on hard coding it may cause issues or reach limits.

Thanks for all the reply's. I think i might make a 2D annunciator panel if i do not see a difference in performance once i move the code to external.
 
Last edited:
No, that's not what I am saying. The DISPLAY of the annunciator is best done in the 3D model. It's behavior controlled by an LVAR. The LVAR is best controlled/processed/set/defined in a gauge. Minimal logic built into the 3D model.
 
WarpD said:
No, that's not what I am saying. The DISPLAY of the annunciator is best done in the 3D model. It's behavior controlled by an LVAR. The LVAR is best controlled/processed/set/defined in a gauge. Minimal logic built into the 3D model.
Click to expand...
Ya the 2D panel would work but i too thought i don't need to go that far.
This is exactly what my original question was and this is exactly what i thought i need to do. Thanks for confirming.

For example instead of 9 conditions for the 1 vis tag in the hard coding. Just have 1 Lvar in the hard coding and put the 9 conditions in the external code so the model has less logic and will be smaller in file size. Which in return better performance.
I have plenty of annunciators i can do this for and i want to confirm before i make this update. Thanks again!
 
You must log in or register to reply here.
Back
Top