I know I asked this question before on another forum but never could get it to work. Can anyone tell me why when I create an object with FSDSV3 try to include it in a EZScenery library it always comes up with the floor separated from the rest of the structure. I have emailed Abacus asking this question and never have received a reply. Thanks.
-
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.
FSDS V3 to EZScenery
- Thread starter rvc68
- Start date
There's a bug in FSDS3 that causes this to happen. It is difficult to repeat on my system, since it does not happen every time, but it is certainly common enough to cause some headaches. I'm not sure if Abacus is working on a fix or not - I wish they had a forum, at least.
Fortunately, there's a workaround:
1. Export your object as a .X file
2. Start makemdl.exe, load you .X file into it
3. Select which options you desire in makmdl.exe (if any)
4. Export as .mdl file
So, yeah, you basically have to manually do a few steps that would otherwise have been done for you. It shouldn't work this way, but it does. Hopefully, Abacus is aware and is working out a fix.
- Martin
Fortunately, there's a workaround:
1. Export your object as a .X file
2. Start makemdl.exe, load you .X file into it
3. Select which options you desire in makmdl.exe (if any)
4. Export as .mdl file
So, yeah, you basically have to manually do a few steps that would otherwise have been done for you. It shouldn't work this way, but it does. Hopefully, Abacus is aware and is working out a fix.
- Martin
There is an update that fixes this prob in EZ called ver 3.53.346..It does not fix any objects that use animation with FSDSV3 though..you have to use the method posted above for that..though still your animation parts will not appear until a re-boot of FS9 after placing them..I think Louis is still on some Island somewhere sipp'in TeQeila..I would be nice if he would at least fire up the ole laptop and help out here..especially the boolean feature!! 
Originally the Bug was with EZ..but the guy who made that got on it and fixed it quick for both G-max and FSDSv3..a fix for (exploded objects) But still its best to use your method and export X file and compile a second time for either animated objects (or) older FSDSv2 objects..there is an update for EZ-- I think its 1.3..and should of been sent to all purchasers of EZ via E-mail
Thanks to all of you for your quick responses. I checked my EZScenery folder and I do have the 3.53.346 update and have had it. I will try the method offered by Shakakoz to see if that works. I thought I had tried that method before but I will try it again and let you know what happens. Again, thanks for all the help.
- Messages
- 34,370
- Country
This is certainly a FSDS3 problem, as I also have it with some old FSDS2 objects I tried to re-export. Abacus is aware of this problem, I have submitted my source codes to them to evaluate.
Basically the problem is that FSDS seems to define parts of the object in their local coordinate system and then translate them with a translation matrix in the correct position. But during the export these matrices are not defined correctly. This causes the next part in the source code to use the matrix of the previous one as well. This part then gets displayed at the wrong location.
I had not heard of that X-file approach, although it is weird that that makes a difference. MakeMDL also uses a X file to create the MDL object, so I would expect that one is the same as the one you can save. But I will give it a try of course
.
I must say I was a bit dissapointed that I could not re-export my old objects to the new MDL format without trouble. Hopefully this problem gets solved soon.
Basically the problem is that FSDS seems to define parts of the object in their local coordinate system and then translate them with a translation matrix in the correct position. But during the export these matrices are not defined correctly. This causes the next part in the source code to use the matrix of the previous one as well. This part then gets displayed at the wrong location.
I had not heard of that X-file approach, although it is weird that that makes a difference. MakeMDL also uses a X file to create the MDL object, so I would expect that one is the same as the one you can save. But I will give it a try of course
.I must say I was a bit dissapointed that I could not re-export my old objects to the new MDL format without trouble. Hopefully this problem gets solved soon.
arno said:I had not heard of that X-file approach, although it is weird that that makes a difference. MakeMDL also uses a X file to create the MDL object, so I would expect that one is the same as the one you can save. But I will give it a try of course
It is odd, however, I tried setting up FSDS3 to work with the FS2002 SDK version of makemdl.exe, and I couldn't get to export directly either. However, when I exported via .X file, I was able to load it into the older makemdl.exe as well.
That's what gave me the idea for trying it with the FS2004 version.
- Martin
I've had success with the .x file and also with setting a single parent part. I did a Lowe's store from plans and had a lot of parts gather in one corner of it. The floor was set the parent part for everything and it didn't work. That was the first time I tried the .x file and it did work. It seems to vary from time to time, but usually one or the other works. If all else fails, merging them all into a single part usually works.
I also had problems placing objects in EZ-Scenery and contacted Abacus. They did reply but did not come up with solutions. I find the only thing that works 100% of the time is to centre the axis to all parts making up a model before exporting as mdl(part menus - centre axis to par). This corrected the exploding models and roofs dropping to floor level etc but I still have inconsistent results when converting FSDS 2 to FSDS 3 in terms of texture placement. Any thoughts.
I saw a post on another forum where the writer moved the axis of all the parts of his object to 0,0,0. Apparently this helped his problem, and would explain a bit of what was happening, and why it affected some parts, but not others.
My export to .X method works fine too.
- Martin
My export to .X method works fine too.
- Martin
