working on a obj mesh with texture mapped.
Attempt to import into V8, necessary to have the existing 1:1 dims open ok in the V8 1:1 dims template.
it comes in but the raster mapping is not right !
go file open and try again and its ok.
However we need the import method for the dims for all V5 projects, (many)
why has import not honoured the texture mapping ?
There are three meshes in the project, the other two see correct mapping.
the bad one was the one ‘visible’ at time of saving in V5, the other two being turned off.
test turn it off then save as suffix visOff.
open in V8
still bad.
Hi,
I am using the link from a recent thread, that Wim picked up on the upload of another mesh.
I am sending the big project , three meshes, and zipped it all up, and clicking the red button ‘upload now’ nothing happens.
I reckon it uploads before that button does anything.
we could do with a progress bar so we know when clicking the button does actually allow something to happen ! tech@mcneel.com was the email address the link showed.
5 mins later and still that button does nothing.
on the tab upper left is a rotating blue circle, 15 mins later and stil rotating.
what other method is there of uploading this to McNeel as this method seems full of holes.
I will try for pcloud instead as this is prehistoric !
at 1Mb/sec ploud also prehistoric.
1.7Gb file to send.
in this day and age is there not anything better McNeel has ?
not following why test is exporting v5 to an obj ?
the problem is a V5 .3dm file that has functional meshes with mapped textures, loses the texture on one of them when the .3dm is imported into v8, whilst file open keeps the texture.
The key here is if the OBJ file has two Textures named exactly the same. if this is the case, then matching them back up can be impossible. We can look closer.
What is the source of this file? What App created it?
Hi,
I will try that link again, but after 1 hour of occasionally clicking the red send button I still had rotating blue circle on the tab top left.
That pcloud transfer should have got through.
I will try again with the rhino link.
its 1.7Gb and zipped.
each obj is a different name, and the file name is also pasted into the layer its on.
no point in creating another as its this project I need to get into V8 and we need to know why it failed on the one obj, when using import mode.
wish me luck, uploading again.
2hr 26mins online calc says for 1.544mbps and 1.7Gb.
initiated 20.35 appx.
Its a lousy interface no indication its happening, click the bitton, doesnt change colour or anything.
Just starts a bouncing left right grey dot on the tab.
there wont be a problem as such as all have different names and correspond to the names on the layers.
the layer with the problem is
NO RULER V2 OBJ M 2.2.0 TypeC MkIII EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6colvert
and the obj is named within it,.OBJ M 2.2.0 TypeC MkIII EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6colvert
hope this sends as apart from a grey dot going left to right, no progress bar, etc.
aha upload done it says, so you have it.
Hi,
glad it arrived.
V5 save file as
file ending in template v3 MESSABOUT.3dm
close Rhino5
Open Rhino8 choose new and cannot see file names so choose something.
then go new and this time get big screen file explorer and readable names.
choose Small Objects - Inches Decimal V8 1to1 ready for V5.3dm
go file import and browse to the rhino5 saved above.
after a few secs it arrives, and as I had saved it with the layer No Ruler V2 turned on, showing the trolley,
the first I see is as in image at start of thread ! wrong image mapped.
I turn off that layer and turn on the ruler obj layer and thats ok, then turn on the non ruler above that and thats ok.
save the file suffix intoV8.
then try process this time using file > open method and its all ok, BUT the dims are a mess.
Thats why i used that template and import as the dims are set up as 1:1 matching the styles and model space dims of that V5.
The method to be used for bringing V5 projects into V8 and having dims behave. Subject of another thread let alone months of angst over V5 into V8.
Hi @Japhy
Having to use V5 for this project, but needing V8 for 20 sec saves versus 2 minutes on V5 though lines far superior, but save time bad.
If I could avoid compression then saves would be 20secs but is there any way to turn off compression in V5 ?
taking ages on this mesh as a result, but not heard back as to the fix for missing texture.
was 13d ago.
Wishing to use V8 here ! having bought it and overcome most if not all of the hurdles now.
Whats the situation please on these imported textures ???
I have been waiting to know of the fix to this as I am finding V5 VERY SLOW and I have LOADS of these to do.
So you are saying when importing a V5 file with obj and allocated jpg texture, and the result is a MESS.
thats as expected ?
What happened on your V8 when you IMPORTED my V5 file ?
I am up to date on V8.
I sent over the .3dm the obj and jpg files I had in use with it, are you saying you imported that V5 file into your V8 (and mine us up to date) and got the mess and that is acceptable ?
What do I have to do so as to get my image visible and work on the project in V8 ?
2 minute saves in V5 us unworkable.
and waiting 20 secs just to go from single view to 4 pane view, surely McNeel doesnt expect Rhino users to have to put up with such ?
I would like to use V8 having bought it months and months ago, having also bought v7 and found I had to go back to V5.
Hi, @Japhy
so the inability to import a V5 file into V8, is not V8 at fault of working with V5, but V5 of having an issue, though it all looks perfectly ok in V5 and works ok, just SLOW.. just doesnt import to V8 and retain the jpg mapping to the obj, (as per my image showing its lost the mapping)
Was this problem known about before ?
So you say the workflow is
Import to V8
save as a V5 (suffix V5fromV8)
import that file with its suffix V5fromV8 AGAIN to V8
all now looks correct, save as V8 and then use V8 on the project ?
Please confirm this workflow.
Anyone importing V5 with obj’s into V8 note this solution !
Note.. file open method works fine, but doesnt allow dims made to 1:1 model space to be honoured, whilst Import route DOES !
I’ve always been of the opinion that its almost always faster and better in the long run to redraw than use legacy or others messy files (this applies to gh definitions, geometry, whatever).
That said, we will continue to help you try and migrate your work, but its going to involve workarounds based on the each individual issue. I don’t see a way to get all of your needs met in one click.
Such as importing the dims, redoing the obj in this case.
Hi @Japhy
When you say redraw, are you suggesting start the project over again and redraw things ?
Not sure anyone would be doing that, IMPOSSIBLE.
as if so that isnt going to happen, years of work to be redrawn, Now I could understand that if it was 1st April ‘april fools day’ !
please explain what to redraw ?
I have loads of work in V5, and V5 is a McNeel product.
and I should be able to use V8 on these projects. Things should be forwards compatible.
I didnt expect V8 to be START AGAIN.
Nobody is going to redo their work.
I have got the dims sorted,
convert all V5 dims of an existing project to 1:1 model space
save file suffix ‘dims 1to1 for v8’
IMPORT this file into V8 having opened a template 1to1 Model space with dims styles matching V5. of the same units and size.
check the test area dims and make any changes necessary .
save as v5intov8
so that leaves LINE QUALITY which at the mo is showing fuzzy areas on drawn items, very inferior to the CAD quality lines of V5, and the ants on 1lb braking strain fishing line for projected lines, (a mess).