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

P3D v4 Help please

P

paul1964

Messages
169
Country
unitedkingdom
I'm still having big problems with my installation, I am unable to export animations. But is there any FSDS users willing to export the fsc to mdl if I send it to them?
Many thanks
Paul
 
me. attach files and send. maybe later I might be able to help through Skype. Package the project (which will then include your fsc file and textures) Bob
 
The main problem i have is that the program will not save the route to flight sim and if i try it crashes. so the work z around is to start the program cancel the fs path window and it starts. assign the texture path through properties and export the project as an x file .
 
that works, but it might be you have chosen the wrong path to xtomdl. I have found two of those in my sdk path. one is under something like 3dsm7 or 3dsm9 or even in bin!!!! I once treid 3dsm9, didn't work, then 3dsm7 .. it worked. another time I hadr o reinstall I had to do just the opposite. OR... an old SDK or a wrong SDK?

I don't know if FSDS will work, pointing to a P#D SDK or not. I'd stick with the l'd FSX SDK. It works fine and compiles a bgl or mdl just fine for P3D4 and up. Show us your animation! Bob
 
in my case it doesnt even work pointing it at the fsx sdk . i even installed fsx again but with no joy. i wonder if it is a win10 problem
 
Sounds more like a permission issue... Try running FSDS in Admin mode. Also, make sure none of the files used to save are in read-only mode (clicking on the Properties tab).
 
Sounds likely, but I ran mine w/o then with... no di9fference, but computers are aierd. ya never know. I just wish I could get FSDS Tweak working again.I click on the last step and the DOS screen starts running then that last screen pops up, I x out of it and the DOS then finishes up. I go to open the mdl .... message... this mdl is not usable.
 
FSDS used to have issues if UAC was turned on since it couldn't write to it's install location - at least thats my memory of it. Have you tried installing FSDS outside of your program files?
 
yes i remember the uac thing with FSDS and because of that its on another drive. Also tried admin mode but to no avail, the only other thing to try is checking the files. I take it you are talking about the files in the program folder?
 
paul1964 said:
yes i remember the uac thing with FSDS and because of that its on another drive. Also tried admin mode but to no avail, the only other thing to try is checking the files. I take it you are talking about the files in the program folder?
Click to expand...
No, I was referring to the saved files that you have created or saved at a previous time. If they are in a "read-only" state you will not be able to re-save it under that name. That is unless you change the "properties" of that file. Normally this would give you a pop-up message stating as such, but FSDS is maybe preventing it to (older software).

You mentioned that you have placed it on another drive, but it sounds like you have also placed it within a "Program Files" folder, which is not any different than placing it in the "C:" drive where "Windows OS" is located.
 
paul1964 said:
I'm still having big problems with my installation, I am unable to export animations. But is there any FSDS users willing to export the fsc to mdl if I send it to them?
Many thanks
Paul
Click to expand...
Just a thought, but when you export are all the animated parts ending up all over the place? If so, then the reason is that you need to assign a parent to each part you're animating and that parent must be placed at the exact x,y,z of the animated part - if you don't do that and you're exporting an FSX model then your animated parts will not be in the same place on the exported model. I use the now ancient, FSDSxtweak to export the project for FSX using the modeldef. FSDSxtweak gets the x file and the modeldef and builds the mdl for you with the extra functionality required for FSX.
 
It helps to start your model with a single reference part and reference all other assemblies and animation datums to that.

BTW you can actually run FSDS and compile models without FSX or P3D on your system at all. As long as you create the folder structure FSDS expects to find.
 
Indeed, so long as you have the SDK and model def referenced, but you'd want to check the output though ;)

So long as your animated part is the child of another part that has the same x,y,z co-ordinates, animations work fine. If there is any deviation of the parent part from the animated child, animations get a bit screwy.
 
Hi the output isnt the problem , its the fact that everytime i start the program i have to go through the same process of locating the texture folder. I then do what i want and export as a x file to MCX .
 
OK, so this may or may not help you - the file paths are stored in the registry:

Computer\HKEY_CURRENT_USER\SOFTWARE\Abacus\FSDesign35\Paths

When you are not using FSDS take a look in there and see if the paths are saved. If they are not, it must be struggling to write the data to the registry. If they are there, then that points to FSDS - but since I've been using it on Windows 10 64 bit for years I doubt it's the software.

Registry on my system says - you'd need your corresponding values:

[HKEY_CURRENT_USER\SOFTWARE\Abacus\FSDesign35\Paths]
"ApplicationPath"="C:\Program Files (x86)\Abacus\FSDS_V3.5"
"ProjectPath"="C:\Users\XXXXX\Desktop\XXXXX"
"FSPath"="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"
"TexturePath"="C:\Users\XXXXX\Desktop\XXXXX"
"ObjectPath"="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\Scenery"
"BGLCPath"=""
"MakeMdlPath"=""
"BglCompPath"=""
"XToMdlPath"="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins"
"FSXBglCompPath"=""
"PresetName"=""
"ModelDefPath"="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.xml"

But if you are unable to modify the registry you might need to make yourself an administrator - and that might be the whole issue to start with ;)
 
Last edited:
You must log in or register to reply here.
Back
Top