We have a large organic model which loads slow and viewport navigation will freeze when viewed on the web, While the desktop of manage does not freeze. Would this be a graphics card issue as some computers do not freeze when others do?
My understanding is the desktop version of manage uses opengl while the web version uses active x.
We all run the latest updates with win 7 and 64bit os and enough ram. I have 24gb my colleagues have 4-8mb. One colleague can view the active x on the web fine and can navigate freely the others cannot,
At first I thought I would need to reduce poly count of the model as it was 300mb I have it reduced to 70mb now and it actually loads slower and the views still freeze.
While merging in all the model components I left out a section that was done in max and has many organic shapes. It loaded slow and navigation was not freezing. after the shapes were added thats when it locks up navigating from view to view.
What i need to know is technical in nature and could be in re to vertices not welded in max or too many polygons or something which causes slow load times and also what causes viewports to become unresponsive.
This model has elements from max and autocad, many came by way of fbx translation out of navis then into max, performing a reduction then back into navis via 3ds
We have developed a wrapper around the modelview for use on the web. It is the web app of navis where the problems exist. I even used the test html to verify results.
I have to think the views working on one and not on another is due to graphics incompatability.
The load times (my other issue) is constant for any machine, it takes almost 1 minute to 45 seconds on a fast internet connect. (fios 30up and 30 down)
We have manage 11-13 I assembled this in 13 and saved down to nwd 11 to upload on the web
The file is too large to post but can give you access via ftp
Please help
Steven Williams
Director of Tech Sales support
EcoDomus