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

MSFS24 Ever seen this with your custom model?

gouaill said:
Thanks Gary for all the explanations. NZQE is really a nice complex designed strip in FS2020 only. FS2024 version has been scaled down.

So then, when you say you found the Haze / Mist Effect, was it in FS2020?
Click to expand...
Yes.
gouaill said:
Attached are the one I found in FS20 NZQE. There were no other appropriate smoke or mist (for falls and rivers) in FS2020. Next step would be to create ourK80 own. The object library you mentioned is great but I try to avoid more and more to force people to use dependencies for my sceneries.
Click to expand...

UPDATE: See the Edits to my post above in this thread on Page-1:

https://www.fsdeveloper.com/forum/threads/ever-seen-this-with-your-custom-model.459929/post-933273



It is possible that the Effect(s) cited above at NZEQ must be custom configured for 2024 versus 2020.

The SDK Docs allude to the unique attributes present in compiled SPB files used in Visual Effects and other types of SPB files, and they admonish us that we may not (should not ?) attempt to use them in 3rd party scenery ...and expect them to actually work.

This 'may' allude to such files as being capable of achieving highly unique configurations specific to current rendering scenarios in MSFS at the time they are 'composed'.

Alternatively, it may infer that they contain code intended to obfuscate efforts to duplicate them (as in ...protection of intellectual property ?).

Based on what (little) I have read thus far on the new format used for "Special Effects" in MSFS in a distinct sense compared to FS2Kx *.Fx files., it seems the SPB file format is a compiled XML code set that is indeed highly capable of capturing multiple elements and parameters which are required to render a MSFS "scene", possibly including everything- and more- than previously captured in Saved Flight *.FLT files in FS2Kx.

So, AFAIK, it 'may' be premature (until we know more) ...to consider an implication of copyright protection having been implemented by Asobo for "Visual Effects" as a deterrent to use of 3rd party Effects in SPB file format.

My initial impression is the SDK Docs are simply stressing that each SPB configuration can be unique to each rendered state of the sim.


As to what happened to the "Haze" / "Mist" / "Smoke" effects from 2020 at NZQE, if present in a 2024 load of the NZQE scenery from the NZ_Simulations Library and Milford Sound, or other packages, the SPB code may have been uniquely configured for the 2020 rendering engine and the parameters set on the developers installation at the time it was 'captured' to XML, then compiled into a SPB as a Visual Effect.

In 2024, 'Lens Flare' Effect near dusk is seen without a specular rainbow of colors; but the shimmering mist and cloud-like haze is not.

The latter attributes suggest the Effects are dynamic, and not a FS2Kx graphical 'pixel orgy' displayed as a kind of cycling *.Fx Sprite.


Thus, my guess is, at best, we 'may' (possibly ?) be able to "re-configure" existing 2020 Effects so that they can be used in 2024.


Otherwise, as you stated above, we may need to re-create them via MSFS SDK tools to meet (different) rendering requirements in 2024.

Based on my cursory glance at the SDK workflow required to simply display Effects, there is no quick and easy way to view existing Effects to see how they run, without first setting up a scenery project through that ridiculous and convoluted "Org Chart Spaghetti" graphic configuration that currently seems to be the fascination of some in the coding community.

I would rather just load up the Effect in the equivalent of FS2Kx "Visual Effects Tool" and display it in the sim at / near the selected user SimObject in a matter of seconds.

Otherwise, I would be glad to use a MSFS-compatible version of Arno's Special Effects Editor feature via MCX, or his stand-alone utility of the same name ...to view and edit Effects.

I do not want to create an entire ecosystem in which to develop a scenery just to view and tinker with the SDK, so I more readily can learn what it contains and what it can do.

Instead of cultivating spontaneity and ease of use, the SDK seems to be MS profiling, tracking, and data-mining gone horribly wrong.


BTW: It might be best to move our latter posts on this un-related topic to another thread in the MSFS SDK or Special Effects sub-forum:

https://www.fsdeveloper.com/forum/forums/msfs-sdk-devmode.155/

https://www.fsdeveloper.com/forum/categories/special-effects.118/

GaryGB
 
Last edited:
Hi,
Yeah, I was using those effects from using the library of MSFS with great success. An example bellow.

Happy to know that Arno produced a tool for that. I hope it will be simpler to make smoke than in the sdk. Will try that for sure.

And I just installed the latest MCX version and it a breeze to produce power of 2 textures and XML textures file!

Much appreciated guys!

... starting a new building for the Grands-Jardins NP : https://images.app.goo.gl/184qdLnLFDooYWEQ7
Ile Genois.JPG
 
For documenting the solution to this issue, here is what I finally found while using the bridge to build another one in a new scenery : this issue was caused by too long lines. The original bridge was about 220 meters long. I reused it to build a bridge 280 m long, and was able by ensuring there was no line longer than about 120 m long. I realised it by making another smaller bridge from the original winthin this lenght limit.
First the new longer bridge at starting my new scenery Parc national de la Jacques-Cartier : https://flightsim.to/file/103749/jacques-cartier-national-park-quebec
JAC-Pont2.JPG


This bridge after lines cut:
Sans titre.png

And the small one that revealed the thruth:
JAC-Pont3.JPG
 
You must log in or register to reply here.
Back
Top