-
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.
FSXA MCX atthpts
- Thread starter Pyscen
- Start date
- Messages
- 34,540
- Country
Doug,
Here on my PC it is still working in the latest version. What I noticed recently with some objects is that they were displaced, so they were not at the altitude I expected them. That issue is on my todo list.
Here on my PC it is still working in the latest version. What I noticed recently with some objects is that they were displaced, so they were not at the altitude I expected them. That issue is on my todo list.
Pyscen
Resource contributor
- Messages
- 3,040
- Country
hmmm... ok was this displacement after a model move? so the front of building is the center? I'll try it without shifting the model first and see what happens.
Thanks
Pyscen
Resource contributor
- Messages
- 3,040
- Country
No still not showing in preview before shifting model,... Using Windows XP lastest update as well,... is anyone else have this problem?
This regard any and all messages considering the above!!! I did a DUH moment! Things you need to know... make sure attpt is "click on"! Allowing it to show! The Dunce cap is on me now!
Last edited:
- Messages
- 1,361
- Country
Hi Folks
Arno/Doug -
I'm also having problems with attachpoints,
and had attributed it to my failing video card.
Now tracked down to a drawing/scaling issue in MCX.
Test in v535
Placing attachpoints visually, ok.
Export model, ok.
Import exported model,
attachpoints numeric coords remain the same,
however now visually displaced
to double the numeric coord offsets before exporting.
PS
re: Object report
Would be more useful if contained more data.
e.g.
bounding box size
crashbox enabled
attachpoint coords
etc.
re: Version Number
Any chance please of including
the build number as the minor version number.
Currently only shows major number 1.2.0.0
Instead show 1.2.535
HTH
ATB
Paul
Arno/Doug -
I'm also having problems with attachpoints,
and had attributed it to my failing video card.
Now tracked down to a drawing/scaling issue in MCX.
Test in v535
Placing attachpoints visually, ok.
Export model, ok.
Import exported model,
attachpoints numeric coords remain the same,
however now visually displaced
to double the numeric coord offsets before exporting.
PS
re: Object report
Would be more useful if contained more data.
e.g.
bounding box size
crashbox enabled
attachpoint coords
etc.
re: Version Number
Any chance please of including
the build number as the minor version number.
Currently only shows major number 1.2.0.0
Instead show 1.2.535
HTH
ATB
Paul
Last edited:
- Messages
- 34,540
- Country
Hi Paul,
That's exactly the behaviour I have noticed as well. As I mentioned I made a bug report to test this further already. I have not tested it in FSX yet, so I don't know if it is a problem in the MDL or just with the display in ModelConverterX.
This is on my todo list already, you mentioned this before. It is currently scheduled for after the 1.2 release.
I would have to check, the application is made before the revision number is added in the version control system. That's why the date of the development release is included in the about screen. I'll check if I can easily do this.
That's exactly the behaviour I have noticed as well. As I mentioned I made a bug report to test this further already. I have not tested it in FSX yet, so I don't know if it is a problem in the MDL or just with the display in ModelConverterX.
This is on my todo list already, you mentioned this before. It is currently scheduled for after the 1.2 release.
I would have to check, the application is made before the revision number is added in the version control system. That's why the date of the development release is included in the about screen. I'll check if I can easily do this.
Pyscen
Resource contributor
- Messages
- 3,040
- Country
Arno,...
One thing I did think of... I think someone has mentioned it before but not sure,... pre sets or saved sets for the material editor,... saved pre-sets for common material setups, somewhat like what FSX SDK shows,... or allow the user to save set-ups,... I would think it would be fairly simple, just a simple text settings and once loaded would bring up the settings in the current material.
- Messages
- 34,540
- Country
Hi Paul,
Yes, they should be the same as in GMax, XYZ. Be aware that in the compiled ASM code the Y and Z axes are flipped, but MCX just has Z upwards.
The fourth one is indicating whether the vector is a normal (1) or not (0). I guess I have to try to hide that when editing, since it is confusing.
Yes, they should be the same as in GMax, XYZ. Be aware that in the compiled ASM code the Y and Z axes are flipped, but MCX just has Z upwards.
The fourth one is indicating whether the vector is a normal (1) or not (0). I guess I have to try to hide that when editing, since it is confusing.