Thank you, I will try that. I always start cold and dark.
I have just learned from my coder that in Sim Update 5 Asobo decided to change the name of the radio templates, without telling anyone 
So that may explain why your radios are not working the way they should.
All fixed for the next update though, so that should clear it up for you.
5 Likes
this explains the same issue in the Bn-2 Islander as of yesterday -lol
1 Like
I think there was the same problem in the JF Arrow III and they fixed it.
1 Like
Yeah, we have had issues with f-15 too, where some switches and knobs, example, engine fuel cut, Nav com swap switches, and many others stopped working because Asobo rewrote some templateâs from scratch. This also affects tooltips too. Before Su5 the Asobo default templates tooltips behaviour were dynamic like heading position degrees, or lights on/off, etc⊠F-14 was affected too but was launched post su5 And you didnât noticed it except the manual sweep wing tootiped as engine anti-ice. F-15 and stearman has all corrected for the next update. We sorry so much about didnât launched hotfix before, but we wanted to be sure, we didnât launch a update that will need a hotfix after next Asoboâs one. Seems that su6 maintains a continuity with these new templates and we can launch the updates without fear
1 Like
there are many affected aircraft including the stock ones. if you take the Airbus for example and you change from selected altitude to managed you will see that the tooltip does not change. There is also a bug that affects multiple planes in which the pitch trim works in reverse when you assign it to an axis. And Iâm trying to locate what is the cause
2 Likes
If you have any contact with the Just Flight guys, they are looking into the cause of the axis swap as well. According to the Milviz guys, it has to do with their using WASM to control their trim and Asobo using the new templates.
Any thoughts on Asoboâs rewrite of the templates? Was it a good thing? Did they fix anything? Are they more âorganizedâ now or something?
Did they screw up the Axis code and thatâs why itâs reversed for so many planes now?
1 Like
-
F-14: has one wasm gauge but not trim inverted.
-
F-15: no WASM at all, but not trim inverted.
-
Stearman: no WASM but trim inverted.
I would dare to say WASM is not the issue.
About this: in my humble opinion, was something totally unexpected as well as unnecessary, and more considering that the pre su5 templateâs system was perfect as it was, and there were no problems that justified a replacement in this area (even if it was for an Xbox release), but just to fix little things. But it is also clear, that being able to have simply improved the previous template system that already worked great, they have been replaced with something that does NOT work as intended or just doesnât work at all: not only dynamic tooltips or animtips stopped to work as intended, but they have also replaced RPN sentences contained in the XML generic templates that called Aircraft variables or Local variables shared with JS code, that previously worked, with others that do not work at all, or changes in generic templates tittleâs names that has not been corrected in each aircraftâs interior or exterior model and because of that, many aircraft are calling templates that no longer exists , or just numerous grammar or syntax errors in many expressions that are detected even by the SDK console as errors or warnings (and this is said by a person whose English is something far from good).
In summary, the game has a rather long list of bugs that in my opinion should be a priority ONE to solve, than getting into something that did NOT need to be replaced at all, or at least from scratch, and that has created even bigger derivatives problems, not only in third-party aircraft but in Asobo stock aircraft too, As if they didnât have any debuggers in their crew to test the versions before releasing them or like if there were no coordination or just zero communication between AsoboâS different members or departments at all. AsoboâS staff have a lot of talent but in my opinion they need changes at the organizational level.
4 Likes
reminds me of the SU3? was it - when âsomebodyâ at Asobo arbitrarily changed the way the flaps worked in the Global flight dynamics of the sim..
2 Likes
Kind of⊠Yes. I tried to replace an aircraftâs interior and exterior model xml files with anothers from other planes just to diagnose, and as expected, somethings stopped to work because of nodes or anim names not matching, but surprisingly the pitch trim started to work. So I rather myself to say the problems are in those templates inside fs-base-aircraft-common
exactly, the flapâs lift coefficient value was raised its effects twice in that update, generating twice the lift and thus reducing the AOA or airspeed necessary to land as direct consequence. sometimes we do not realize how a simple change generates a domino effect on the rest if we donât test it enough.
1 Like
I was only saying what other developers said about the subject. I didnât mean to suggest that was the issue with your planes.
1 Like
So it sounds like two types of templates were rewritten from scratch, the cockpit animation templates and the tooltip interaction templates. And, it seems, as far as you can tell, the rewriting of the animation templates was unnecessary and added no value, and broke things along the way?
The tooltips I imagine were rewritten to bring them in line with Xbox interface standards. Similar to using people avatar shapes for airplanes that they used to do, IOW, somebody whoâs clueless about actual human interaction with an airplane completely rewrote the interface without any UI usability testing?
Iâd have to agree with that, like the white outline around displays, and the dot.
no, I have expressed myself wrong, I sincerely apologize. I mean that there is indeed something that is reversing it, and maybe in their case WASM could be the cause because although it may be written in C# they still have to call the templates, so it can be directly or indirectly related.
I personally donât use wasm, and while I have some scripts in xml, I could perfectly encode them in the htmlui folder in the javascript files, the language used at the end is the least, but you end up using or calling those templates, or the simplane.js file etc.
Nope, I understood what you meant. I was just afraid you thought I was trying to say it was WASM related.
1 Like
I give you an example:
this is the code that fix the transponder knobs issue (donât tke into account node_ID or anim names):
this is the old code:
Before, we called the template once for the four digits, and now we have to split this in four calls, one for each digit, because the base template was rewritten. The question: was it really necessary to rewrite this base template?
1 Like
iâm going further, nav com swap button:
left one is the old template we were calling, and right one is the valid which is working now. As you can notice the fix is just a change in the templateâs header name.
I return to the same question: what facts justified this change? Didnât they realize how a tiny change would affect stock aircraft or third-party developer aircraft? Who was the enlightened one who thought it was necessary to modify the name of the template and did not take into account that we were going to have to correct it later by deduction?
2 Likes
A320âs altitude knob template:
If you notice, for each position of the knob there is a tooltip, up arrow, down arrow, turn left and turn right. In the new Asobo templates, animtip or tooltipid no longer exists, however this template has not been fixed. and thatâs why you donât see those descriptions in the a320 or any other airliner that needed to use this template, that would explain why in some aircraft you see a dot or the white outline as you mentioned.
question: just ⊠why Asobo did this and what was the purpose?
2 Likes
Youâre all gonna love this
CodenameJack447 and I have included new engine parameters for the faired Stearman to replicate the higher performance of the Wasp Junior radial engine, and I have ( with some help from Asobo ) got smoke working in the simulator, just needs some tweaks to the smoke effect generator and the product will be updated, should appear next week on third party stores, a bit after that on the marketplace.
23 Likes
Could we expect to have these updates (engine, smoke) with the actual design too ?