make mdl path

[gww53]

I uploaded the newest development release this morning, extracted the zip file as I always do ( I thought), and I now am unable to export dae file to the mdl. The dae imports and processes normally, night rendering, lom, etc is fine, but when I try to export, failure

I get the error attached, can't find the fs9 makemdl path.
MCX defaulted to a folder c:/fs2004sdk which does not exist on my computer.

I've searched the site, now that the wiki is working hoped the manual would have an answer...but I can't find it.

I have only FSX and the FSX SDK installed--always have. I never owned FS2004. I have processed 200+ models through sketchup--mcx--Librarycreator, though none for a month or two.

The only reference to fs9 I find is in the fsx root directory (attachement). I've searched entire computer for makemdl with no success.

I am sure I've read of this or maybe even dealt with it myself before, but I can't find makemdl anywhere on my computer.

Where am I forgetting to tell MCX what to do? I can't find a "FSX only" box, etc.

And looking at paths, I may have a problem with a need for fs2004 bgl path as well.

Sorry, I know this has been addressed but I can't find it.

Much appreciate the support, and the fantastic program

Gary

 

[gww53]

Partial solution

I finally found that on the reinstall, when I now choose "export object", MCX had defaulted to 2004, not FSX. I thought I was set. Export, "are you authorized", no error message. It appears that the 2004 sdk files are irrelevant

I can now export the model with no error... but the created mdl is unreadable by MCX. Older models, bgls, etc. that I've made can be read.
And I can process an old DAE, export it , and the mdl is fine

I think it must be a problem with this particular DAE file. I recently updated sketchup, so that may be it. I'll try on the weekend to make a few simple boxes in the new sketchup and see if they work.

The mdl has file size of only 3 kb while the parent dae is about 550

The dae looks fine in mcx, and processes etc. Just can't succesfully export it to a readable mdl with today's or 12/19/2013 mcx (the only two zips I have)


Sorry to bother, I suspect it is something in the new sketchup/this building

Gary

 

[arno]

Hi Gary,

Good to hear you fixed the first issue. Sounds like you had selected fs2004 mdl as format to export, not fsx mdl.

Not sure about the second problem. Are there any messages in the event log when you export?

 

[gww53]

There is an error message on export--had not noticed yesterday. I'm uploading an image (not sure if it can be read) as only part of the log is recorded when I "export event log at closing"—it cuts off at the statement “Crashtree no granularity specified”-and the error messages follow!! I can only copy one line of the event log at a time.

Seems that with this sketch up project, XtoMDL is unhappy.

Also note a warning at lower left ATT COR CUR COR. There are not any attached effects on this project (lights, etc). Not sure what that refers to.

I’ll try a new model this weekend..seems something in this project is conflicting, as old dae files work . I’ll explore if it’s the new sketchup (13.0.4812)

Gary

 

[arno]

Hi,

The error message is string buffer length to big. So I guess some part is to complex for xtomdl. I haven't seen this before. How many triangles does your object have?

 

[gww53]

It's really a pretty simple building, but I' surprised, compared to some other projects, it does have quite a few tirangles--1618.

If anyone wants to try, I'll attach the sketchup file as well.(nope, looks as if neither dae or skp are valid upload extensions)

Just got home from work. I'll do a simple model later tonight or tomorrow to see if it's the new sketchup or not.




Thanks, Gary

 

[gww53]

Sorry for the double post, I guess I can zip the sketchup file

 

[gww53]

Seems there is a problem with the particular sketchup model. Just made another, exported and all is fine.

The failed building was started using the "add geo location" tool of sketchup--you go to the airport via a google earth window of sketchup, "grab" the building of interest and it "lays it down" on the sketchup "canvas" so the base dimensions are real easy--just outline with the line tool and drag to height. Pretty sure this is the first time I've started a building that way.

The model I just made which works is just a freehand rectangle "pushed" to height.

I wonder if the geo import adds conflicting info, or triangles, or other info I needed to handle differently?? By my standards, the model of the KEMV restaurant/fob that failed is better than most of my projects (that's pretty sad!!!!!) and if I could save it, I'd try.

I'll try a geo import tomorrow--sorry to bother but surely appreciate your input.

Gary

 

[arno]

Hi,

That amount of triangles for sure is not too complex. That should export fine.

Good to hear it is only this model that gives trouble. Hopefully you can figure out what makes it fail.

 

[gww53]

Sometimes the blind pig finds the apple….

It appears the problem with this model was that the NAMES of some of the texture files were too long.

If I imported the DAE and immediately exported, all was fine. If I import, convert all of the jpg textures to power of 2 and export all is fine. If convert to power of 2 and save as dds, all is fine.

But when I add project name (in this case, modern_glass_brick) to the texture names, the export no longer works. I re-saved the sketchup file/dae with a short name, and all works well.

I’ve never mastered texture sheets, and when I have MCX create them, my night textures are checkerboards of no texture in FSX. I’ve accumulated a huge collection of jpg textures, and of course there is http://www.cgtextures.com/index.php!!!. So, my mdls all have 6-12 textures, each pasted and manipulated into sketchp.

As I reuse textures, but often change color or size, I have mcx rename them so they are unique in my library/scenery/texture directory

So…. I get “modern_glass_brick dark_stone_no_mortar.dds” or the like!

I didn’t figure out the “cut off” for too long, but I’ve attached the directory (above) which failed and the mcx object info that worked.

In the past I have messed things up with blank spaces in my file names (and you kindly fixed that as a “bug” [as in “idiots bugging me!!”]. We (I am the king) idiots should keep our file names under a page long.....

Gary