V8 file import V5 file loses OBJ texture mapping when File open works

[Japhy]

@Steve1

When you say redraw, are you suggesting start the project over again and redraw things ?

I was providing my anecdotal experience in bring projects forward, across various softwares. We often get ‘this project is just like this old one, just copy it to save time’, the reality is it would have been better to start from scratch. I don’t know if this applies to your situation or not.

What is your workflow like in this regard? Do you have 1000’s of parts that you are looking to bring forward?

@Steve1

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.

Each major version has major SDK changes, we try to keep backward compatibility as much as possible but after several versions that gets harder and harder to do. Rhino 5 was released in 2012 and updated for 5 years, things have changed a lot since then in Rhino as well as the supporting platforms.

[Steve1]

Hi,
following your method.

1. import the V5 file with its three obj’s and their mapped textures.
2. looks a mess,
3. save the file as a V5 file.
4. open that file, BUT STILL A MESS
5. select the obj and look at its colour allocation, update the jpg by copy pasting in the full address taken from V5 (see image below)
6. Rhino 8 crashes, error report appears so send details of what I was doing.

NOW IF i CANNOT EVEN ALLOCATE THE JPG TO IT AGAIN, WHAT DO I DO ?

This is serious !

Please try this exact same series of steps as you have the V5 file I sent, also the obj and its jpg.
The one I tried to update the jpg to is the lowest of the three objs in the layer palette.

the full addresss to it on my PC was
V:\Agisoft Projects overflow\Agisoft Type C Mk III nearside front brake assy East Kirkby\OBJ Mshape 2.2.0 Type C Mk III EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6\OBJ M 2.2.0 TypeC MkIII EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6colvert.jpg

and I pasted that into this window, was that the correct place to paste it ?

I try again and remove the entire jpg address as initially an obj can have nothing allocated to it (well it can in V5 !) and then one does the browse to jpg and all is good, and instead of being just the mesh , V8 CRASHES AGAIN !
Steve

[Japhy]

@Steve1

import the V5 file with its three obj’s and their mapped textures.

this isn’t going to work. Import the OBJ into Rhino 8.

You’ll notice if you then save as Rhino 5 and Open/import into Rhino 8 it behaves as expected.

[Steve1]

but the obj has been scaled rotated and all sorts done to it, I cant repeat all that again, it would never match all the work drawn to fit it and done over it since.

The same would apply to the other projects using obj’s.

Please test at your end on this file and see what the heck is going on.

and establish method to reimport it and MATCH IT EXACTLY TO WHAT IS ALREADY THERE.

also what method finds the address of the actual obj I used ?
I have struggled to find a way of seeing the address of the obj I imported into Rhino, and without Rhino telling me that I cant even reimport it !

I have started pasting their names into the layer names but prior doing that I dont know which obj I used.

Steve

[Japhy]

Trying some alternative methods to get the large mesh in. Using the GH import is interesting.

[Steve1]

Hi,
keep trying, see what different methods work.
e.g what if you try V7 (which I have) then go V5 to V7 to V8 ?

I dont use Grasshopper so would need a step by step to the method, and not be told learn grasshopper.
and how would that deal with my dims as at least we have that going as wished for now.
Import works, open doesnt.
something that takes 1 minute !
or have a thingy set up I use to convert.
else I will be in V5 land forever.

as file open, on this file, shows the obj perfectly ok, and file import is a dogs breakfast, but is needed for the correct looking and size of dims,
is there a method with those two that gets the best of both worlds ?

I have tried this..
1, file open the V5, mesh is good.
2. select mesh and export selected as good mesh v8
3. file new 1:1 dims small objects inches, import the V5, delete the wonky mesh.
4. file import the good mesh v8.
5. stil bad.

Damn !

try clipboard instead
1, file open the V5, mesh is good.
2. select mesh and go edit copy, and WAIT AND WAIT. eventually its done
3. file new select template 1:1 dims small objects inches, import the V5, note location of layer and delete its layer with the wonky obj texture.
4. edit paste, and the layer reappears, move to where it lives in stack.
5. turn on layer AND ITS GOOD !

So why does it work via clipboard and not via being export selected ?

I did try for all three layers in one copy to clipboard but had to end task V8 as it forever doing it !

So I now have an imported V5 so correct dims, then a viewable texture on the obj. in the EXACT location and scaling etc etc that it had in V5.

Just the awful bitty lines and thick lines to solve now.

Steve

[davidcockey]

There is not a fundamental problem with opening in Rhino 8 files containing large, textured meshes which were created by Rhino 5.

I opened in Rhino 8 a .3dm file by Rhino 5 which has multiple large textured meshes. The meshes were originally created and textured in Agisoft Photoscan, then exported as textured .obj objects. The meshes were subsequently imported into Rhino 5, scaled, rotated and positioned. The results were saved by Rhino 5.

I used the texturing created by Agisoft Photoscan, and did not alter it in Rhino.

Mesh totals: 6 meshes, 7889528 vertices, 14999998 polygons
Open double precision polygon mesh: 521754 vertices, 856864 faces
Open double precision polygon mesh: 2118947 vertices, 4143135 faces
Open double precision polygon mesh: 470411 vertices, 756109 faces
Open double precision polygon mesh: 2189603 vertices, 4243890 faces
Open double precision polygon mesh: 1016376 vertices, 1909629 faces
Open double precision polygon mesh: 1572437 vertices, 3090371 faces

[Steve1]

Hi David,
yes file open works fine.
but doesnt bring ih the dims at 1:1 model scale and their styles.
File , select the template with 1:1 V5 dims, then file import, brings in the dims and they are all as they were in V5, but the obj is all messed up.
however as just posted, delete the wonky obj layer, and edit paste in the good obj from the V8 file open method one, and all is then fixed ! (though copying the mesh takes AGES.

Can I ask…does your Agisoft Metashape make soft out of focus areas on the mesh viewed in their prog, where the photos were pin sharp ? Photoscan never did that, BUT TAKES 9hrs when metashape 30 mins.
and does metashape fail to align some photos which if one then uses Photoscan they all align ? last project 28 failed and Photoscan aligned all.

as mine does, even on a new POWERFUL pc built for Rhino and Agisoft mesh handling.

I have ‘Standard’ ,..and despite flagging this problem up with Agisoft, nothing has ever been done to solve it. did so again with files etc three weeks ago, and all goes very quiet ! two fundamental problems.

I wonder if Metashape exported obj’s are the cause ?

What with that and V8 its doing me in.
Steve