Simple as that . I am creating this new post as an rephrasing of earlier one.
Carefull reading of online SDK documentation + DA62 MOD sample + WASM Airplaine sample implies there is , somehow, a streamlined , direct way of accomplishing the use of the MODULAR Aircraft design.
Not so , at all. At least , I have not been able to create a Variant of an existing Airplaine to which I could later add an custom wasm gauge .
My experience so far has brought me to “ An selectable , flyable , not visible apart from Pilot Helicopter “ . Ab d it flies ok.
Yes , a flyable Lonely Pilot, like in the movies.
In my experience I would say :
I just ran into:
hidden container rules
undocumented preset inheritance behavior
attachment resolution quirks
vendor folder magic
CFGCompiler file-definition limitations
streamed package restrictions
content type mismatches
SimObject category inconsistencies
project editor vs packagetool differences
This has been a several days and hours of “circling around”
If anybody out ther can help me descipher this , I would be very thankfull
im not certain what your trying to do or what restrictions your running into …
but it sounds like you just want to create a New preset (which can create a new ‘variant’ selection), then you can ‘attach’ anything you want thru the attachedobjects.cfg file
the da62 mod is a great example, though you may not need an attachment folder for configs
many of the edits for those files can be done right from the preset folder i think
understand the way the da62 mod works is its added directly into the original aircrafts folder structure- with the modular system it kinda becomes a base part of the package when loaded, make sure you new mod does the same (follows the target aircrafts folder structrure) and it should work
" there is , somehow, a streamlined , direct way of accomplishing the use of the MODULAR Aircraft design "
this isnt how i would describe it
what they do is insert a portion of the configs into the target aircraft so that it uses the original base aircraft with these few edits
Agree , in fact I returned to my “DA62_mod_working” project copy example as a clean valid platform to insist in my quest. ( the variant created as per sample with my own ui identifier ) he he
At first glance , I noticed the prominent “attachments” procedure of the sample but abandoned it because of some own missunderstandings of rules I had. And that was a bad call…..
So, your comment is most valuable and brings me back to that arena.
Thank you and have a nice day. Will report my findings.
PS: To answer your first comment , what I am trying to do is to create an variant of “any” existing streamed aircraft ( helicopter is my goal ) to provide a new identival version of it , untouched and legal and finally add custom developed WASM gauge to it . I have the wasm gauge procedure fully understood ( from the wasm aircraft example ) and just need that variant to start experimenting on it . Using the DA62 although I like it and fly it regularly is just not an helicopter.
for the wasm, it will probably need to go into another folder i think
going by this it could be placed in the common/wasm or in an attachment folder but not in a preset
but that may only be for 2024 wasm files? not sure, ive seen some still in the panel folder iirc
You’ll need to be a bit more specific about what you want to do, and why it’s not working, and what you’d expect to be happening. It’s a bit hard to help you decipher anything if you yourself are being vague and cryptic.
It sounds like you just want to add a WASM gauge to an already existing aircraft?
If that is the case.
-Make a new preset
-Make an attachment that has your wasm gauge in it if it’s a visual gauge.
-add attachment to preset
as EZRyder said, as long as you copy the original aircraft folder structure, it should work fine
@kcgb Thank you for your interest Sir. And I would like to appologize for beeing “vague and cryptic”. ( I would have thought the title was telling enough).
To all of this enigma , now solved , I would like to say “There is not anything fundamentally wrong with 2024 nor its sdk , it is just a different animal “ And for a hobbyst dev like me, comming from the 80s it is hard to be that open minded when assesing sdk .
Happily , thanks to @EzRyder s tip, looking closer at the sample was the driving force to solve my problem . Thank you for that @EzRyder . And that i got ealier from Mr @EPellissier . “Samples are , indeed the key”. Also valid for the wasm aspect.
A visible gauge inside the cockpit is another bridge to cross will try with another specific post.
Thank you all , it was a tough ride with an very rewading outcome ; I have got my variant ( preset ) with custom wasm code running in it, without abusing the franchises legal boundaries.
Have you all a nice day
Francisco.