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

Effect display disparities - FXEditor/MCX versus In-Game

Hi Arno.

Could you please investigate/add the following issues to your TODO list.

When attempting to create several effects
I've encountered various disparities in supported behaviour
between their rendering in FXEditor/MCX
versus their rendering In-Game.

N.B.
Following results were only from testing in FSX/FSX-SE.


-------------------------------------------------------------------------------
Effects per Controller -

Controller support for numbers of effects.

FXEditor/MCX - Supports over 500 effect.#
In-Game - Supports 100 max effect.#

See attached -
- Screenies - ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER
- Zip content - _ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER.fx
Contains ONE controller, calling FIVE HUNDRED effect.#

Please limit FXEditor/MCX support to effect.100


-------------------------------------------------------------------------------
Controllers per file -

FXEditor/MCX does not honour Controller.#
and will only render the final controller.# in any file.

FXEditor/MCX - Supports ONE controller, (renders final controller only).
In-Game - Supports MULTIPLE controllers.

See attached -
- Screenies - ODG_FX_TEST_5_CONTROLLERS_1_EFFECT_PER_CONTROLLER
- Zip content - _ODG_FX_TEST_5_CONTROLLERS_1_EFFECTS_PER_CONTROLLER.fx
Contains FIVE controllers, each calling ONE effect.#

Please implement FXEditor/MCX to support multiple controllers.


-------------------------------------------------------------------------------
Error trapping -

If possible, please add -

For VARIABLE = MIN, MAX

1 - Test MAX is equal to, or greater than MIN.

2 - Test that MIN and MAX values are numeric.
i.e. are ZERO, not OSCAR


-------------------------------------------------------------------------------
Many thanks for all your great work.

ATB
Paul
 

Attachments

  • CAP437_01_FXEDITOR_FAULTY_CODE.jpg
    CAP437_01_FXEDITOR_FAULTY_CODE.jpg
    64 KB · Views: 179
  • CAP437_02_FSX_COMPLIANT_CODE.jpg
    CAP437_02_FSX_COMPLIANT_CODE.jpg
    64.4 KB · Views: 179
  • ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER___01_FXEDITOR.jpg
    ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER___01_FXEDITOR.jpg
    89.9 KB · Views: 184
  • ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER___02_IN-GAME_1.jpg
    ODG_FX_TEST_1_CONTROLLER_500_EFFECTS_PER_CONTROLLER___02_IN-GAME_1.jpg
    55.2 KB · Views: 172
  • ODG_FX_TEST_5_CONTROLLERS_1_EFFECT_PER_CONTROLLER___02_IN-GAME_1.jpg
    ODG_FX_TEST_5_CONTROLLERS_1_EFFECT_PER_CONTROLLER___02_IN-GAME_1.jpg
    46.9 KB · Views: 170
  • ODG_FX_TEST_CONTROLLERS.zip
    320 KB · Views: 89

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi Paul,

Thanks for the detailed feedback, I have added them to the FXEditor bug/todo list.

They don't sound extremely complex to implement, so I'll try to make some time soon to work on them.
 
Thanks for considering these further enhancements, Arno. :)

PS: On the issue of limiting 'sprites', you may recall the somewhat humorous discussion by an 'FSInsider' linked from this thread:

https://www.fsdeveloper.com/forum/threads/people-as-effects-problem.432696/post-697238

Another pertinent consideration (...and caveat !) discussed by an ACES blogger:

http://blogs.technet.com/b/torgo3000/archive/2006/01/25/418037.aspx

"Q: How come I can't see all of the sprites in the incredibly elaborate and perf intensive effects that I've created?

A: Being the effects artist for Flightsim (among many other duties), this one has bothered me to no end. We have a sprite limit cap that is determined by your effects quality settings (in the display setting dialog). This is for performance reasons, because it is incredibly easy to kill perf using tons of facing sprites. Unfortunately, because the volumetric cloud system are volume clouds of facing sprites, they got thrown into this budget (this is a bug, and our bad). So here's how you hack it. Put an "effects.cfg" file in your effects folder with the following contents:

[Sprite Limit]
Medium=500
High=9999999999
Low=100

Then set your effects settings to high and watch the billions of particles bring your system to its knees.

DISCLAIMER: I am not responsible for any fried hardware or lost wages caused by the minutes per frame display you may achieve using this trick. However, I will be fully responsible if you end up with beautiful visuals and not much of a performance hit. [;)]"


GaryGB
 
Last edited:
Top