My question to SDK team:
Is it possible to add an opportunity to create FLATTEN LAYER for Custom Created Ground Polygons (manually or automatically)? This needs to avoid flickering of FLAT custom polygons over ground mesh.
Regards
My question to SDK team:
Is it possible to add an opportunity to create FLATTEN LAYER for Custom Created Ground Polygons (manually or automatically)? This needs to avoid flickering of FLAT custom polygons over ground mesh.
Regards
Would it be possible to add short range planar reflections to the sim? There are cases where screen space reflections and cube map reflections are not sufficient, particularly gauge glass reflections. Neither of these reflection methods work properly in cockpits. They both look entirely incorrect.
If this is not possible can you please reinstate the ability to apply parallax rendering to translucent objects so that accurate reflections in gauges can be ‘faked’? This worked perfectly pre-SU5, but was unfortunately removed with no explanation in that update. After SU5 applying the parallax material to any translucent object results in that object being incorrectly rendered as a wireframe.
Thanks!
The ground textures always have the same kind of grainy asphalt effect on it… is there a way to show different kind of “hard” ground materials like concrete and smooth asphalt?
Agree! I also would to ask Asobo about “detail mask”. You are right, all sceneries have same ground detail texture - asphalt. But we need more different kind of groun materials…
Would be amazing if Asobo open opportunity to create own “detail mask” by 3rd party developers.
A post was split to a new topic: Do I need an up-to-date SDK to fly in MSFS?
Are you considering an update on the “painted lines” in future? Its quite a hassle making realistic lines for airports since many of them are different, "e.g. yellow, yellow with black edges, new v/s old paint. it would be great if we can apply similar transparency and aging effects to lines.
Simconnect should be able to handle all types of LVars and Events, not only B-Events.
Is there a way to expand the SDK & Simconnect variables for aircraft 3rd parties so they can develop the complex airliners. Before launch there was a lot of talk about exposing variables that were closed in previous versions but it seems like Aircraft 3rd Parties still have large sections of the SDK missing for complex airliners, is this something that is going to be concentrated on?
Hello,
In the Asobo fs_base native object library, is it possible to provide a version of the objects intended for night marking, ( Tips, Taxy_light, edges )… which can light up at night !!!
It’s good to have this multitude of nocturnal markup objects available, but if they are not linked to a lighting effect, it is currently limited use ! Thanks
Update … OK finaly I find the way for light up your objets … but the road to acces to this fonction are little bit complicated … I never imagine find it at botom Airport Objets, under Light Presets Wip !!
But working great !
SDK Documentation
Are there any gains by replacing the quality of mesh to 1 meter source in the USA?
What was the source mesh used in World Update II USA?
Do you have a timeline / overview of the documentation you are working on (html/js, weather, mission scripts, etc.)?
Will the fairly low arbitrary limit on the number of engines (four) be raised? (I am working on an aircraft with six (XB-70), but eight would be great for some other aircraft (B-52 at least), and twelve even better (Do X).)
Can you commit to fixing the problems in bundled aircraft and airports that show up in the dev mode console window as errors and warnings?
Please improve the quality of Projected Meshes. The resolution is currently very low.
Please allow Aprons to render on top of Projected Meshes.
Increase the resolution of TIN Meshes so we can terraform it with the same results as Non TIN areas.
SDK DOCUMENTATION: thanks for the great job you’ve done already building such an open system. Can the SDK documentation be improved for:
Model XML templates (e.g. a detailed example of actual use, including what was necessary in the model such as standardised node names or animation names, plus the hooks available to add custom code)
Sounds - the Wwise system really is a new complex system to learn compared to playing wav files based on vars - a SDK example/tutorial would help a lot.
Missions
Could you please start removing from SDK documentation all mentions of things that aren’t even used by MSFS2020. Comparisons to older versions of Flight Simulator should be in separate documents. There are developers (like me) who have entered the scene only with MSFS2020, and their number will naturally increase over time. For the long-term health of the product and its add-on market, the SDK should be optimised for new developers. Confusing them with references to how things were done in older version is not useful.