[Michel Wuest]

Hello NextLimit again

I have withe the new version 1.5 still the same obening problem for mxs and mxi Files (See the description further below). I am allone with this stange thing ???? First of all could somebody from NextLimit response me?


My System: MAC 2.33 GHz Intel Core 2 Duo, Mac OSX 10.4.9

1) If I generate a new mxs, I mostly save the mxs-File (from SketchUp) on the Desktop. Then I can open the file from the Desktop. If I move the mxs ore mxi in an other directory, i can't open the file. I have the message: "Corrupted Mxs - This mxs is obsolete or has been corrupted". But if I move the File back on the desktop, i can open the file again ?!?

The same problem also with mxi

So can me somebody help or can you please correct this Problem? I can the Files just open at the place of creating.

Very, very strange!!!

Greetings Michel

[Kabe]

Hi Michel,

that's strange indeed. Are you opening the MXS with Studio or the Renderer?

Do you have the same effect when writing out the MXS again with Studio to
another place on the desktop, then move it again and try to open it?

If you can move the MXS then, the the SketchUp plugin should be the culprit.

If the error pops up even then, you might have something special in your scene.
Could you eventually provide an example scene then?

Hope it helps to nail this bug down

Kabe

[tom]

This sounds like a strange operating system issue. Maxwell has no built-in feature to question from which location you're trying to open the scene. As long as it's provided correctly by the file system, it will be able to read it. Have you tried it on another computer or reinstalling your operating system?

[Kabe]

Reinstalling your operating system?

Please don't. It's highly unlikely that this will solve anything on OS X.

Kabe

[beatriz]

Michel, if you have no other computer to test get in contact with technical support to arrange a way to send us the file so we can test it
http://www.nextlimit.com/tech_support.htm

Does it happen with any scene?

[Boris Ulzibat]

I have a problem with paths on Mac OS X too.
Cinema quits when Maxwell plugin is installed and i try to open file browser to open a file or to change a path.
Wonder if these problems are connected...

[Becco_UK]

Michel Wuest: Reinstalling an operating system on any computer should always be considered a last resort, particularly so if you are only having problems with one item of software.

Might be worth correctly removing Maxwell and its plugin from your system though and reinstalling those.

I assume you know about the Maxwell 1.5.1 OSX update which can be downloaded from the maxwell download page.

[tom]

I know suggesting a reinstall doesn't sound like a decent technical support. But as you may agree there are times this could be necessary even if only one software is having the problem while the others are not. If you wonder why I thought that could be really helpful, it's because nobody else has this issue so far and technically speaking Maxwell really has no chance to make a preference on source paths. With another computer it could work because it's obvious the rest of users don't have this problem. And reinstalling the OS might help because I see no reason it could be hardware dependant. So there are 3 things to investigate. 1) Maxwell, 2) OS, 3) Hardware. So from my above explanations 1 and 3 are obviously proven they cannot be the reason. But this is my approach and of course it's your risk to try. I could be completely wrong, just trying to help.

[rdesign]

With all due respect to Tom, reinstalling the OSX system should be done only as a last resort- only after you've tried absolutely everything else.

If Kabe's suggestions don't help the problem, you might try one of the following (if you haven't already):

A. Repair permissions (with Disk Utility while logged in, not from the OSX install DVD) and then restart
B. Zap your PRAM (hold down Command-Option-P-R while restarting until you hear the second chime)

If those don't help with the MXS problem, try:

C. Restart in Safe Boot Mode (holding down the shift key while restarting)

If that doesn't help, try:

D. Create a new user, restart and log into new user; see if that user still has the MXS problems you're having.

If after all that you're still having the problems I would completely uninstall Maxwell, and reinstall it again.

Hope that helps.

Regards,
Tim

[Becco_UK]

Michel Wuest: I'm going to repeat this - reinstalling operating sytems is a last resort.

If you must then check if this is going to invalidate any warranty on your machine.

However, all problems with newer operating system are usually repairable as long as the thing initially starts up which yours is.

[Michel Wuest]

Hello together,

First thanks a lot for every bodys help. Now i think I have found the bug.
The problem are really the exported mxs files from SketchUp. This files, i can just open at the "born-place". So if i open this exportet mxs in Studio and save it under a new name, then the problem are gone. I can open this new mxs at every destination.
So for finding the bug, i have both mxs files for downloading with the follow names:

1) File named "file_corrupted.mxs" >> can't open in a other folder, just at the born destination (this example on my desktop). The link for this file are here:
file_corrupted.mxs

2) File named "file_ok.mxs" >> just "Save As.." in Studio with a new name. Now i can open this file every where. The link for this file are here:
file_ok.mxs

I have just saved the exported mxs form SketchUp in Studion with a new Name. The Problem for this file are gone.
I saw that that the resaved file with the new shorter name are biger.

file_corrupted.mxs = 419'699 Byte
file_ok.mxs = 419'842 Byte
>> Difference = 143 Byte !!! > That means, something in the new file are different !!!

So the bug must be in the SketchUp Plugin for Mac. This problem i have with each new exported mxs form SkechUP. Actually I'm happy to now, that i just have to open this generated mxs form SketchUp in Studio and to save it (Save As...) with a new name. I did also test to klick just on save with the same name. That didn't help.

So i hope you guys from NextLimit can correct that.

Thank's a lot
So long
Michel

[tom]

I don't know what does it mean but the file you provided as "file_corrupted.mxs" is working here and under any path. Can anybody else having same configuration with Michel test it as well?

[Michel Wuest]

Hello again,

Well now i don't understand computers. That thing with renaming did just work one time. I tried the same with a ohter file. Now this trick don't work anymore?!?!

So I tried this things from Tim:

A. Repair permissions and then restart >> Didn't help
B. Zap your PRAM >> Didn't help
C. Restart in Safe Boot Mode >> Didn't help
D. Create a new user >> Yes that did work, after some things:
More about D:
If I copy the "file_corrupted.mxs" on the highes Harddisk-Level (Mac HD) in PC that would be C:, i could also open this file in my normal User account.
Well i did change in the "new user Account". I tried to open that "file_corrupted.mxs". It didn't work. I had the same message "Corrupted Mxs" in Studio.
Ok now the reason. I tried to copy the file "file_corrupted.mxs" to the desktop of the new user account. A window appeared. I had to enter the administrator password. Ok after i had entered the password, i could copy this file on the desktop of the new user account. And what to you think what happens? I could opten this file "file_corrupted.mxs" and in any folder!
Now, it seems to be a file-access-right-problem.

I tried to change the access rights in my normal User Accout like in the new User Accout. I also did change to my User Name it didn't help. Well I don't now realy witch Owner i have to select. There are to many from the System: System, amavisd, appowner, appserver, clamav, cyrusimap, daemon, eppc, jabber, lp, mysql, and...and...and..and..

I'm now realy sure the problme is with this file-access-right.

I hope, you form NextLimit, for example Tom (> I'm not sure if you are a Mac-Crack ) can help me.

A other thing for Tom (Next Limit). I work at a Architectual-School (We also have Computerscience in the same house) and I also teach Students in SketchUp and Maxwell. That's very new. We have at this scool a new big Sun Computerfarm with about 200 CPU's. The operating Systm on this Machines are Solaris 10. Would it be very hard for you Next-Limit Guis, to compile the maxwell Render, Server, Manager for this System? I did ask this question in this forum about three weeks ago. But i didn't have a response. A other question, have you Guis a e-mail, which i can use for this question and for sendig the Adress of the school? For this Answer you can also use my private mail which i had to enter for the maxwell registration.

Greetings

Michel Wüest

[Michel Wuest]

HEY NEXT LIMIT -- I HAVE FOUND THE BUG !!!!!

The problem is not the file-access-right, which i thougt first. No it's the umlauts in German. We use in german sometimes Ä,ä,Ü,ü,Ö,ö.

> If the file name contais one of this Letter (Ä,ä,Ü,ü,Ö,ö,.....) the mxs, mxi can't open.
> If also a mxs or mxi without the Letters (Ä,ä,Ü,ü,Ö,ö,.....) is in a Folder or Subfolder, which is named with some ore one Letter of (Ä,ä,Ü,ü,Ö,ö,.....), the mxm can't open.

Tries it self. Rename any mxs or mxi or folder which contains a "normal written" mxs/mxi, with a name, which contains a ä,ö,ü, and you cannot open this file on one mac any more till you rename it without this letters! I don't know, if there the same prblem on a windos PC with german.

AND TOM, please read my second thing in the last message above, at the end.

Now i think you Next-Limit-Team can correct this bug
And send me a spanish beer for finding the Bug

Greetings

Michel