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

MSFS20 Code / Scripting Languages Used for Things Like "Fallback="

CBris

CBris

Messages
104
OK, this applies to any version of Flightsim I guess...

As the title indicates: I would primarily like to know how the "fallback" path in cfg should be used, but I would also be interested to know which programming language is used - perhaps I can get me a "Dummies Guide". Would it be xml?

As for texture.cfg - there are several lines of fallback used and there are paths indicated by fallback.xx=..\texture - where some fallbacks have one or two or several sets of ..\

At the moment I can't get fallback to work. I have to copy all the original "master" texture images into my edited repaint. I have been given to understand that fallback should cause the sim to check the textures currently in the texture folder, compare the contents with the master texture folder, usually something like: F:\msfs\Official\OneStore\#####\SimObjects\Airplanes\#####\TEXTURE and then load the missing files into the "community repaint"

Anyway, it's not just the configs texture folders that are of interest; there's also the aircraft.cfg and others like panel, sound, model...

Also: sometimes the .json files cause msfs failures if there's a comma too many in the manifest.json - and maybe the various other little lines of script like "date", "package_size"

Apparently Asobo has these defined somewhere too, but it seems to be like a freemasons club - if you don't know the right handshake, you don't get access ;) - so is there a separate information repository somewhere, rather than each little bit of code getting answered separately all over the fora and then disappearing in the haze?

Nice to know, possibly vital too.
 
As for the fallback entries in texture.cfg. I can confirm that it works well. Except for animated people, I can instruct all my SimObjects to find the textures in the main textures folder:

mfs_sdk_fallback_texture.jpg



This saves me a few textures, because the textures do not necessarily have to be in the TEXTURE folder of the SimObject. The only exception are the animated people, unfortunately the fallback strategy does not work (jet?). But the animated peolple are composed of a lot of bones and a skin/mesh modifier. However, my windsock is also a skin/mesh animation object. But here again the fallback works :)
 
Hi Chris (DBris).

It's good to see you around again, as we all try to explore inland from the 'shores' of this unfamiliar new domain we've arrived at called MSFS-2020. :)

Specifically, the .\ or ..\ (Dot and Backslash) characters are good old DOS - Windows parlance as Directory (aka "Folder") Path hierarchy designations

Path (computing) - Wikipedia

en.wikipedia.org en.wikipedia.org


PS: I'd love to see a "EagleSkinner" MSFS-2020 livery set for the Christen Eagle as well as the fictional USCG Aerosoft Beaver livery if / when you're inclined in the future. ;)


IMHO, there should be a lot of fun new releases for MSFS-2020 as the SDK evolves, and our skills working with the new sim develop in coming months /... years. :cool:

( Dot-Slash intended ! :laughing: )

GaryGB
 
Well, I am sure the Christen is on DB's todo list for Iris - I have already given him the go ahead if he can use my existing liveries and if not, I will convert. Beaver? Which one did I paint that on... Aerosoft? AH? Default?

As for all those slackbashing path definitions... would it help to use the "proper" text based path?

i.e. fallback.xx=F:\msfs\Official\OneStore\asobo-aircraft-flightdesignct\SimObjects\Airplanes\Asobo_FlightDesignCT\TEXTURE

Ah! Perhaps that is where I am having problems - my msfs is not on c:\

As for me learning to slap a dollop of paint on the msfs beasts - ye gods! What a mess. Well maybe not if you're a code geek... but there are path names sometimes well beyond the win 10 260 character limit (if your Win 10 isn't up to date). Here's just a couple of w-i-p

experiment3.jpg


17.jpg


This one makes me scream - mirrored wings!!
thumbnail.jpg


Now that I am learning a bit about Blender, I am also discovering stencils and generally painting on 3D models. I am learning a lot of new stuff first, before I can even think of publishing anything I think fit for msfs. I know a lot of (ahem) "repainters" are already pumping outr masses of liveries, but to be brutally honest, a lot of them are mere colour fills of the "livery decals" and/or simple cut and pastes of RW copyright logos, emblems and trademarks.

All good fun though. Now I think I could do with a glass of Uncle Elmer's No. 5 reserve... or a botlle perhaps.
 
CBris said:
Beaver? Which one did I paint that on... Aerosoft? AH? Default?
Click to expand...

Indeed, it was the Aerosoft Beaver.

CBris said:
All good fun though. Now I think I could do with a glass of Uncle Elmer's No. 5 reserve... or a botlle perhaps.
Click to expand...

Even after 8 Hours Bottle-To-Throttle (...or was that ElMer-To-LVar ? :D), I may also need your livery with the aircraft part labels as a reference for my pre-flight walk-around inspections, what with the demand a MSFS-2020 SDK learning process places on ones time, energy and memory. :)

GaryGB
 
You must log in or register to reply here.
Back
Top