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

FSDS3 Quirk (carryover from FSDS2)

S

Sarge

Messages
8
Country
us-florida
Has anyone but me noticed that when setting the radius for a tube, FSDS goes off on it's own? Case in point: creating a peaked roof for a taxi-in military hangar, "feet" selected. Radius = 87.5, length = 175, Points/Section = 3, Sections = 1, close Left/Bottom/Front tic'd, close Right/Top/Back tic'd, Z-Axis tic'd.

Everything comes out exactly how it should according to the parameters I gave FSDS EXCEPT the radius. FSDS came up with 75.xxx for the radius somehow. This occurred in FSDS2, and now I've just noticed that it occurs in FSDS3 as well. It's not a major problem, as selecting Point mode I can manually adjust the radii. But (I'm not a programmer, understand that up front), if a piece of data is called for, I would expect it to be used; otherwise, why ask for the input in the first place? Just randomly calculate some distance FOR the designer, with a note in the help files that the designer needs to switch to point mode and enter values HE/SHE wants them to really be.

If FSDS isn't going to correctly use the input, then the programmers wasted a lot of time coding up that box for the input. They could have just automatically set up a value, put whatever they wanted in there, then advised the user to switch to Point mode and adjust the values.

Nit-picking, but it's annoying when you're into a design "rhythm" and then have to hit the mental PAUSE button to undo something that should have been done correctly the first time around.

(I've nothing better to do, today; can you tell? :rotfl: )
 
Hi there,

I just tried this and I had no problems with the radius. I think I see what you are talking about though; The radius being the distance from the center of the object to the furthest extent of the point on my traiangle. After I did this, I wondered if it was the bottom part of the triangle that you wanted to be 87.5 on either side of the axis. If that is so, then this is not the radius, and that is why your objects don't match up. You'll just have to resize it bigger.

SDO_ex1.jpg


If this isn't the problem you are having, maybe you could post a screenshot or two.

Also, for export to bglcomp.exe, you should make your objects in meters, since blgcomp.exe doesn't know which units you have, and assumes they are in meters. It just makes it a bit easier later when you don't have to scale them.

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