Talk:Particle system
Jump to navigation
Jump to search
Issues & Development
|
I have been unable to run FG with particles enabled since a long time due to random crashes in the particle code. — Csaba Halász (Aug 1st, 2011). Re: [Flightgear-devel] startup crash in SimGear (with patch?).
(powered by Instant-Cquotes) |
|
|
|
I actually had it disabled for a long time. After enabling it recently, I also started having memory issues — ThorstenB (Aug 1st, 2011). Re: [Flightgear-devel] startup crash in SimGear (with patch?).
(powered by Instant-Cquotes) |
|
|
|
Drawback with our current codebase: Our integration of the particle systems need to be rethought as this contains geometry with culling disabled which makes a pagedlod just never expire. Switching the particle systems off works pretty good so far. — Mathias Fröhlich (Jul 21st, 2012). Re: [Flightgear-devel] Rendering passes question.
(powered by Instant-Cquotes) |
|
|
|
IIRC each particle > system is attached to the scene graph in (at least) two places: at the > emitter's location in the graph and in a global vector of particle system > updaters. IIRC they are never removed from the global list of updaters > (a bug - but a hard one to fix due to concurrency issues). > Tim knows more about this. — Anders Gidenstam (Apr 16th, 2011). Re: [Flightgear-devel] OSG caching.
(powered by Instant-Cquotes) |
|
|
|
If I'm not mistaken the particles issue has been around since we got particles, so it is apparently not that bad (leak and race condition) in practice. — Anders Gidenstam (Apr 16th, 2011). Re: [Flightgear-devel] OSG caching.
(powered by Instant-Cquotes) |
|
|
|
I guess the issues with "Effect" objects is probably worse than with particles. There's a larger number of Effect objects - and each is connected to a texture (.rgb/.png images) - which may occupy a lot of memory. Just by starting at KSFO, loads of KSFO terminal textures - and textures of 15 different MP aircraft immediately stick in memory... |
|
|
|
Regarding precipitation - the current particles code in Simgear has major performance problems - and some outright mistakes in its implementation. Notably the animation of the particles is done in the wrong phase of OSG’s frame loop, which can prevents particle animations being unloaded - i.e can cause tiles to never be unloaded. For this reason many people have been disabling particle effects to ensure stable frame-rates. However, the complication is the Simgear particle system is effectively a fork+edit of the osgParticle system, which I think is what we use for precipitation. Ideally we’d use the osgParticle system everywhere (since it has correct interactions with the rest of OSG) but it also has the issues about customising the rendering you mentioned. (I don’t think the Simgear particles are any better in that regard, but I may be wrong) — James Turner (Oct 13th, 2014). Re: [Flightgear-devel] Precipitation issues.
(powered by Instant-Cquotes) |
|
Stop contrails from glowing at night and blinking at daytime
Suggestions by Mimino on Pinto's FlightGear Discord server.[1] I have not tested it myself, but do not want it to get lost over time.
I have a suggestion for Particle system#Example:
How to stop contrails from glowing at night (because of <lighting>false</lighting>) and blinking in the daytime (because of <lighting>true</lighting>):
<emissive>false</emissive>
<lighting>false</lighting>
Add inside <color> of <start> and <end>:
<red><property>/rendering/scene/diffuse/red</property></red>
<green><property>/rendering/scene/diffuse/green</property></green>
<blue><property>/rendering/scene/diffuse/blue</property></blue>