- Messages
- 50
- Country
-
Would it be possible to import an SKP file directly to save the process of exporting/importing?
-
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.
Direct Sketchup support
- Thread starter rob hyrons
- Start date
- Messages
- 50
- Country
-
flipping the idea, as sketchup allows 3rd party add-ons, can you get model converter x to work inside sketchup, would love to see object placement in scketchup! Simdirector is buggy as hell, i woiuld be nice to work on a project all in SketchUp then just hit save to BGL and textures boom done 
=rk=
Resource contributor
- Messages
- 4,475
- Country
-
Model Converter X already uses 3rd party addons; XtoMdl.exe, for example. MCX provides a "graphical user interface," for what are otherwise "command line tools," which is the exact same thing Sketchup does for it's tools. So you would actually want to get the tools to work in Sketchup and leave MCX behind, no need for a GUI to work a GUI, agreed?
Pyscen
Resource contributor
- Messages
- 2,994
- Country
-
Hello...
Yes, agreed... if Rob is referring to the object placement specifically though,... it would be easier if someone could write a ruby script to access to a map,.. but then you run into licensing agreements etc... By which was gone with the latest update of SketchUp...
This was known by Trimble when they bought SketchUp... The agreement upon purchasing SketchUp that Google would continue with access of their maps for 5 years... after that it was up to Trimble to furnish the maps etc...
I'm only assuming that is the reason of the idea in the first place.
Yes, agreed... if Rob is referring to the object placement specifically though,... it would be easier if someone could write a ruby script to access to a map,.. but then you run into licensing agreements etc... By which was gone with the latest update of SketchUp...
This was known by Trimble when they bought SketchUp... The agreement upon purchasing SketchUp that Google would continue with access of their maps for 5 years... after that it was up to Trimble to furnish the maps etc...
I'm only assuming that is the reason of the idea in the first place.
- Messages
- 32,883
- Country
-
I have considered this in the past and technically it seems possible. But for the moment I don't see a big need to work only from SketchUp. SketchUp models often need post-processing for good performance anyway.
- Messages
- 310
- Country
-
Hi guys,
I can think of one thing that would be useful but it would work within Sketchup with a Ruby script (I presume) and not require any changes to MCX.
In spite of my best efforts, while building complex SU models I typically end up with a few textures that are slightly 'out of square' and these create additional unnecessary textures. MCX can create a texture sheet for these additional textures but the ability to edit these textures, say to create LMs directly from the .psd is lost. My solution while working in SU is to do a quick export from SU, then open the .dae in MCX using the wire frame view to find the offending out of square textures. Now I can go back to SU to fix them and confirm my fix in MCX. It would be great if a script could be written that would export the SU model while working in SU and open or refresh the export in MCX. There are other reasons to check things in MCX as I work too.
I can think of one thing that would be useful but it would work within Sketchup with a Ruby script (I presume) and not require any changes to MCX.
In spite of my best efforts, while building complex SU models I typically end up with a few textures that are slightly 'out of square' and these create additional unnecessary textures. MCX can create a texture sheet for these additional textures but the ability to edit these textures, say to create LMs directly from the .psd is lost. My solution while working in SU is to do a quick export from SU, then open the .dae in MCX using the wire frame view to find the offending out of square textures. Now I can go back to SU to fix them and confirm my fix in MCX. It would be great if a script could be written that would export the SU model while working in SU and open or refresh the export in MCX. There are other reasons to check things in MCX as I work too.
Pyscen
Resource contributor
- Messages
- 2,994
- Country
-
Hello...
The best thing to do in this case is to use the texture import function, having SketchUp use your psd file for example... I don't have the means to explain better... but it's through the paint bucket icon...
Hopefully... that makes some sense... otherwise, Will explain better upon returning to home computer .
The best thing to do in this case is to use the texture import function, having SketchUp use your psd file for example... I don't have the means to explain better... but it's through the paint bucket icon...
Hopefully... that makes some sense... otherwise, Will explain better upon returning to home computer
.
=rk=
Resource contributor
- Messages
- 4,475
- Country
-
I believe he means to "re-import" the edited texture, but if not, it is my solution. So you have your skewed texture in SU and you already have the correct layered image in PS, save this to your working folder. Now select the edit tab for the texture in SU, but instead of using the export to editor function, select load from file, navigate to your PSD texture and replace.
Pyscen
Resource contributor
- Messages
- 2,994
- Country
-
Thanks... that's what I was referring to
.After doing what rk said... you might have to realign the texture... Also from where this was done you can adjust the size of the texture if need be.
Last edited:
- Messages
- 310
- Country
-
Hi Guys, Just to confirm, I do what Doug and Rick describe. In SU I just keep updating my psd saves as I work.
But here is a little oddity that I discovered: when using .psd directly in SU, if a texture is skewed, when you export and open the model in MCX typically another version of the entire .psd texture will appear in the Material Editor. This can make finding the offending texture area difficult if it's very small. My solution is to temporarily save the .psd as a .tiff without layers (but with alpha if there is one) and reference that. Now when I export to MCX, the Material Editor will show only the offending texture area instead of the full area of the .psd and finding the skewed texture then much easier. Once I've fixed the problem I then go back to the .psd for further work on the SU model.
Another clue to a skewed texture is that if you export the dae using the .psd texture, areas that are skewed will often have very bizarre textures as seen in MCX. But this does not help much if the texture area in question is very small--- as they usually are. I often can't find them in MCX just by looking for odd textures.
But here is a little oddity that I discovered: when using .psd directly in SU, if a texture is skewed, when you export and open the model in MCX typically another version of the entire .psd texture will appear in the Material Editor. This can make finding the offending texture area difficult if it's very small. My solution is to temporarily save the .psd as a .tiff without layers (but with alpha if there is one) and reference that. Now when I export to MCX, the Material Editor will show only the offending texture area instead of the full area of the .psd and finding the skewed texture then much easier. Once I've fixed the problem I then go back to the .psd for further work on the SU model.
Another clue to a skewed texture is that if you export the dae using the .psd texture, areas that are skewed will often have very bizarre textures as seen in MCX. But this does not help much if the texture area in question is very small--- as they usually are. I often can't find them in MCX just by looking for odd textures.