Argaeus
-
Posts
103 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Forums
Gallery
Blogs
Articles
Store
Downloads
Events
Posts posted by Argaeus
-
-
-
-
28 minutes ago, Marten@Stairport said:
This wasn't the one I wanted to direct you to, sorry. Here are the links:
I tried it at Gate G9 and A11 in LTFM but it is a new WIP unfinished version. Either of the above should be good enough to test (all Center gates with 2 or more jetways at piers)
Regards.
-
-
9 hours ago, Marten@Stairport said:
Can you please provide me the scenery and parking spot for a test?
And you guys can test the attached xml
You can test A350 with my LTFJ (Gates 201 to 208 - not A or B stands) or LTFM (All gates with 2 or 3 jetways) sceneries. You can find them here in the Threshold downloads.
-
14 minutes ago, Marten@Stairport said:
They changed the identifier tags in the acf (again). Don't ask me why they do it with every update, quite annoying. We will have to update the config with the next SAM version.
I guess it can wait, no rush. Luckily we have one working door anyways :)
-
On 7/18/2020 at 12:25 AM, AVC29 said:
Sorry to bring this up again, but with the latest version of SAM (updated just now), and the new release of the A350, also just updated, I am unable to connect to door L2, and the jetways are not in the correct place for L1. How can I fix this?
I have downloaded the updated Aircraft.xml linked above, but the issue still remains. Door L2 does not appear as an option to connect to, and the jetways for L1 are incorrectly placed.
I am using my own VVDN scenery https://forums.x-plane.org/index.php?/files/file/53661-vvdn-da-nang-international-airport-vietnam-sam-wt3-ready/
Hi Marten,
Same issue here, A350's old problem is alive again. B789 Magknight in the same position have no problem with connection. Testing my new scenery with different add-ons I own.
-
Thanks.
-
(I see that you are more active here than your mailbox, I am just posting my message here)
Hi Marten,
Are you planning to update SAM to 2.0.8 soon or is it going to take some more time?
As I used subject "revised" items that you shared with me recently in my scenery it does not open up in other users' systems and in most cases causes CTD.
Is it ok if I share these items in proper folder structure so that people can copy the files to their Plugins folder? Unfortunately I had to hide the scenery for the time being.
Regards. -
It is an automated link to SAM_Library which is added by SAM itself. You should disable the option in SAM settings and create your own link in Custom scenery folder.
-
-
6 hours ago, Marten@Stairport said:
Confirmed and fixed for 2.0.8.
When do you plan to release your scenery? Meanwhile you can replace the objects in
Custom Scenery/SAM_DeveloperPack/dockings
Resources/plugins/SAM/lib/SAM_Library
with the ones attached.
FMT-AVDGS-3.5m.agp 373 B · 0 downloads FMT-AVDGS-4.0m.agp 371 B · 0 downloads FMT-AVDGS-5.0m.agp 371 B · 0 downloads FMT-AVDGS-4.5m.agp 371 B · 0 downloads FMT-AVDGS-2.5m.agp 375 B · 0 downloads FMT-AVDGS-3.0m.agp 373 B · 0 downloads
Thanks Marten, I still have too many to add so I will use the new ones for them. I have already added more than 150 of the Honeywell ones around the terminal so I'll just leave them for now.
This project (LTFM) is the one that I already uploaded to the Gateway and now decided to add SAM jetways (finished as of now) and Marshallers/DGS panels to it.
-
I filed a bug report at your website (stariport) but I think there is a problem logging back to it so wanted to share my problem here as well.
The problem is with the FMT(5.0) DGS and before deciding on which type to use in my project, I placed one of each to my scenery using WED and tried to start up the sim to no avail - CTD al the time (I tried at least 5 times). Then I removed all but 1 to test each and only CTD happened with FMT, all other 4 DGS showed up perfectly fine. Tests were run with previous SAM plugin 2.0.6 and also the same happened with the current v2.0.7.
I cannot attach the files as they are long gone now but you can probably get them from your website attached to my bug report.
-
Pls check your Message box.
-
Yes I did use the same template as above. Only changed certain values for a couple of connections but not for the one pictured in my initial message. Attached the sam.xml file here.
-
7 hours ago, Marten@Stairport said:
But you could use the default laminar jetways in case they fit. Users will obviously need the worldjetways addon to get them animated but still better maybe?
They fit alright as facade application is much more flexible in terms of sections and directions. I remember reading in one article that you preferred SAM objects to be used in sceneries rather than Laminar's. Further, SAM has many options in height but Laminar has only one standard height of 4.5 m.
May be you could do only the "rotunda" as an object in matching heights so we can attach 2 separate connection bridges with an angle easily. :)
-
-
I took some screenshots while trying to add jetways to a new scenery and these are the results. At least type 1 4.5 m glass does not align with the doors. Tried B738 Laminar, Zibo 738 and Ultimate 737 and 739 along with FF B777 200LR.
Last 2 shots to show stages of penetration into the fuselage to Zibo B738.
-
I have spent some time this morning trying to find the best fit for a new scenery but I am stuck with either a "straight" jeyway connection facade from SAM library or a "fixed height" (4.5m) multiple choice connection facade from X-Plane lib.
Is there a plan to create an angled rotunda connection with support in the middle as shown in the attached screen shot (Laminar lib facade) instead of a "split" corridor that SAM currently provides?
Best regards.
-
Will keep these in mind. Item 1 seems to be the case for me.
-
I forgot how many times this had happened today I always re-start X-Plane to avoid hick-ups. I do not use "re-load" function too much.
-
Is there a specific reason why I am getting duplicated coordinates for a single item when trying to add DG? Here are 2 screenshots to show the problem. v2.0.1
Regards.
-
In the meantime
-
PS. This might have happened after OpensceneryX update. Just FYI.
SAM 2.0.9 Crash to Desktop on scenery loading
in Bug Reports
Posted
There was a statement from Marten re the crash issue in which he wrote the problem is within XP1150b17 and Laminar knows about the situation. Revert to 2.0.7 for the time being rather than re-installing the whole sim, I still have 2.0.7 and it works perfectly fine with b17.