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

animation question- attn arno

jyarddog

jyarddog

Messages
2,388
Country
us-washington
I made a dumb looking hangar with 4 doors. The two center doors really don't open as far as I'd like them to, but that's my learning process in FSDS. Using Arno's wonderful CAT utility I finally got the doors to quite opening automatically. They sit still until I engage my radio freqency. Voila! They start to open. I found I had to be very close since I did not do any bounding box, but I'm fine with that right now.

The problem is this.... when I turn off the required radio frequency the doors SLAM SHUT instead of closing nicely. Is there something I missed in CAT, or is it something I didn't do in FSDS? Inquiring newbie wants to know! Hehehe! Bob
 
Hi Bob,

I have heard more reports for the closing animation not working correctly. I guess it is time that I take another look at the code to see if it is not some sort of bug :).
 
Hi Bob,

I took a look at the code, but I can't reproduce the problem yet. Did you apply the frequency as a animation condition and did you add other conditions as well? Besides that could you verify you have the latest version (1.2.12 should show on the opening screen).
 
Arno- I hope I am relaying this info correctly. After I installed the program I made a shortcut and put that shortcut in a folder I use for my design work. This way I have most if not all the stuff I use to design sceneries in one place. I used this shortcut to make the animation conditions. I just now checked ... it says it is V1.2.11. I found another icon in a folder (I think this was from the CAT patch) I used this one and found it to be V.1.2.12 which I think is the newer one.

Using the older one I used animation triger in two screens. The second screen I used said this is for the trigger and when this no longer applies the animation will reverse. In both screens I used nav2 clicked the arrow for the code then entered 1200h in both boxes.

I skipped second condition. Also- no bounding box was used.

Now- here is where I really get confused, choosing the correct asm file. The video says to stay away from the 0_cat.asm. The others I see are _temp.asm. modules.asm (which I assume is the asm file that came with FSDS, _temp (an mdl file which I think was from my last asm attemp, _temp_0.asm. Somestimes I chose the wrong file. When I compiled I got the runtime error 13 and everything disappears. Just now I chose various other asm files. I compile - file command not found but it ends up compile ready.

Main point... When I generate my hangar with the doors and all I've installed that in my EZ scenery manager library creator. Then I used the CAT program. When it looked like it was succesful I would rename the mdl file I found in FSDS and used that in EZ scenery library creator and overwrote the other file. I ended up with a hanger with doors that open but when nav2 is changed to another frequency the doors don't close... they slam shut. Bob
 
Here's what I got with the old icon V1.2.11. Should I move the new icon V1.2.12 into scenerydesignorg folder to replace the older icon(v.1.2.11) then use the new one from there? The info below brought up no error messages this time but the info below seems to show nothing but errors.
I may just be following directions wrong. It took me a while to learn EZ scenery manager library program. When I did learn how to use it I picked myself in the butt when I realized how easy it was to use. Me- with two college degrees... boy! I'm almost smart! :) Bob
Starting compilation...

Microsoft (R) Flight Simulator BGL Compiler Version 8.00
Copyright (C) Microsoft Corp 1981-2002. All rights reserved.

Assembling: C:\Program Files\Abacus\FSDS_V3\_temp_cat.azm
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1223) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1223): Include File
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1262) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1262): Include File
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1301) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(1301): Include File
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(2592) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(2592): Include File
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(2844) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(2844): Include File
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(3096) : error A2006: undefined symbol : _local_varbase_1
LOCAL_BASE_32(4): Macro Called From
C:\Program Files\Abacus\FSDS_V3\_temp_cat_0.asm(3096): Include File
BGLC: Error!

Compilation ready!
 
Hi Bob,

Version 1.2.12 indeed comes from the patch I released. What you should do to install it is just copy it over the cat.exe that was installed before (the 1.2.11 version). After that your original shortcut should also point to the latest version.

It sounds like you are using the nav frequency as both the animation condition and the animation trigger. That is not really a good idea, as that could indeed result in the reverse problems you are seeing. Try to use it only to trigger the animation.

About the errors you post, these usually result from using an ASM file that has no animation defined in it. For FSDS you should indeed use the _temp.asm file in CAT. After CAT made a new MDL file you can give it a more logical name and put it in your object library.
 
Arno- Wonderful! I certainly will do this. Will report back with results later. Thank you! Bob
 
Arno- at compile I am still getting those erroe messages in the read out, but it always ends with 'compile ready!'. I used only trigger and used the patch. Doors open by themselves and then slam shut. It does not wait for the nav2 command. I also notice the FSDS folder gets loaded up with more _temp_cat_cat_cat.asm files. Each time I try this one more cat name file is added. Is this normal? Here's a jpg of that fsds folder. Bob
 
Last edited:
Hi Bob,

You should never use the ASM files CAT already tweaked as your input again, that does not work (and might explain the errors).

Always tweak from the origional FSDS/MakeMDL generated files.
 
The 2nd to the last screen in CAT asks for an ASM file only. I browse to where FSDS put the mdl file. CAT won't see it even when I choose 'all files'. I've tried choosing temp.asm, but I keep getting those error comments in the output window. My last post I posted a screen shot of the files CAT opens up to without navigating elsewhere. I've tried a number of them. I guess I keep choosing the wrong one? Bob
 
The file created by FSDS, I assume, is the _temp.asm file. it seems this is the one to use, but by using it I still get the messages. Therefore I would conclude there is something I am doing wrong in setting up my conditions. Perhaps this is right? Bob
 
Hi Bob,

Did you maybe export another object since you exported your hangar? That would overwrite the _temp.asm file, as FSDS uses it for each object it exports.

The errors you get are usually the result of trying to convert a file that contains no animation. If you are sure the ASM file you use is from your hangar, could you please attach them here on the forum, then I can see if there is a bug in CAT.
 
Arno- I made sure to delete any _0cat.asm files and _temp.asm files. Compiled my mdl for my hangar file called hangar-ani.mdl, went back to the FSDS folder and the _temp.asm file reappeared which I guess is the file created when I compiled the hangar-ani.mdl again.

This was my first attempt with animation. It really is not too hot. I could not get the two doors in the middle to open as far as I wanted. I'm slowly learning. Anyway, here's the file/files, and again thank you for your patience and great help. I do appreciate Arno's School of Hard Knocks! :) Bob
 
Last edited:
Woohoo! No error messages! Now... do I use _temp.mdl or _temp_cat.asm? I would guess I use _temp.mdl. Bob

--------------------------------------------
Just now I used temp.mdl. hangar showed up, but I'm back to doors automatically opening, not waiting for my NAV2 switch. Doors open- then slam shut and start opening again. I think I did something wrong in making the animation. Maybe I messed up the frame sequence or something. Ah! Learning is painful, is it not?! Hahaha Bob
 
Last edited:
Hi Bob,

If you used the compile MDL button in CAT you will probably also have a _temp_cat.MDL by now, that is the one you should use. Or maybe it is a good idea to rename it to something useful like hangar_cat.mdl or so.

If you only have the _temp_cat.asm and _temp_cat_0.asm, then you need to compile the MDL yourself with BGLC_9.
 
Hi Arno- Well, I compiled an mdl with FSDS. Using CAT I get _temp.asm which is an mdl file. I also get _temp_cat.asm which is an asm file. Also I get the ones with the 0's which we avoid.

If I use _temp.asm (the mdl file) and use that in my ez scenery manager to add to my library I get the hangar with the doors opening by themselves and slamming shut.

I just now used _temp_cat.asm (an asm file) in bglc9. I got a bgl instead of an mdl. Should I use this bgl and try to make an mdl with it?
Then I tried the same file with makemdl. I got errors.
 
attn Arno

Voila! Success! I made another hangar just to experiment with. Bor is it awful looking! :rolleyes: I just threw it together to experiment with door animation.

I went to FSDS folder and deleted any and all cat files, _0cat files, cat text fiels etc. I left the cat modules file, assuming this is an FSDS/cat related file needed to see asm files; maybe I'm wrong there but its says module... I leave it alone.

Got done with my hangar, paying close attention to set-frame process, compiled and went to CAT. Compiling in cat I chose the _temp.asm I thin it is, but it's an mdl. Chose my trigger, compiled and it worked. Went back into FSDS folder and found _temp_cat.asm file but it is an mdl. I used THAT one and renamed and compiled with EZ scenery mgr. I placed the hangar with EZ and also with Instant Scenery. Worked! It seems that Instant says the files are there and no need to restart FS9. However, it seems that if the object has animation then it still needs to restart FS9 to see the animation. No problem there.

My doors open on trigger and close on trigger! But it does take a long time for the doors to start moving for open or close. Is there any way to speed up reaction time to the trigger? Also I assume I could create a bounding box so I can be a bit farther away from the hangar.

My other problem deals with the speed of opening and closing- this is on me. I just have to change how far I move the doors between each animation frame.

Now it's back to school and the drawing board to find out how to make overhead doors move. Much appreciation to you Arno for all your help. Bob
 
Hi Bob,

Good to hear it is working now, but I find it a bit weird that you compile MDL file has a ASM extension. It sounds like the compilation in CAT did not went as it should in that case.
 
attn Arno

Arno- I may have stated this incorrectly. I used the _temp.asm file to compile in CAT. This gave me a _temp_cat file which turns out to be an mdl file, but it did not say anything about being an asm file. My error. I take that one and rename and enter it in one of my libraries. Works fine.

I made a little shack sometime ago... just a very basic, small building in which I placed a Huochin ground power unit. Just now I added a door to this shack which I animated to hinge at the ground and drop down to the ground. I used bounding box. Drive up and the door opens. Drive away and it closes.

Only one question. Is there any way to get the animation to start sooner on opening and on closing? Bob
 
Hi Bob,

jyarddog said:
Only one question. Is there any way to get the animation to start sooner on opening and on closing? Bob
Click to expand...

If you gave the bounding box the correct size already, the answer is no probably. The timer (counter) of the animation also runs when it is not active, so that means that the CAT tweak can only start the animation once the timer has started again. This can cause a little delay.
 
You must log in or register to reply here.
Back
Top