Re: Fail transferring to DETAIL mode

jaihoyoo · ‎08-05-2016

Like written in the subject, I cannot move to DETAIL mode from SCULPT mode.

I can work on multiple tree under SCULPT mode but when it needs to move to DETAIL mode, then there is a specific layer it fails to do the job.

- I can find this small box shape asking me to 'Check conversion'

- Right below corner there pops up with with Conversion error, but then I do not know what to do next.

KR

Jaiho

Michael-GG · ‎08-08-2016

Hello Jaiho,

if you can't change to Detailing, then your T-Splines can't be converted to Nurbs. This can have several reasons. Problem areas should be shown in red on your model. The conversion error message in the bottom right should also give you more information about why the conversion fails. "Make Uniform" and "Repair Body" with the "AutoRepair" option might be able to help (available under "Utilities"). Also, self intersections of your T-Splines are forbidden. In such cases you need to move your points to fix the shape.

Please let me know if you should still the issues after this. You can also share your model, if you like to, and I can have a look.

Best regards,

GG

Michael G.-G.
Manager Quality Assurance Automotive

jaihoyoo · ‎08-10-2016

Hello Michael

I think I have solved my problem with transferring to DETAIL mode.

Instead of fixing my model ( like I told you in earlier message, I do regularly correcting my model with ' Rebuild' and 'Auto Fixing'), I exported my model in .tss format.

And imported this model from new document.

So it worked, all error messages were gone and easy to move on to both DETAIL and RENDER mode without loosing this 'history'

But there were some changes.

1. Lost all names of my layers

2. Canvas , Analysis and other etc layers are gone only surface data is there

But I am happy that i can work with DETAIL mode now.

I have questions here....

1. Can you explain me with this .tss file?

2. Is there a way I can bring my Canvas layer to new file instead of setting new one manually by myself?

3. Can you export to ALIAS with Canvas layer?

Thank you

Jay

Michael-GG · ‎08-10-2016

Hi Jay,

it surprises me that exporting/importing via .tss fixes your problem, but well, good for you it works. 🙂

Yes, layer information, analysis and similar get lost, those are not supported in the .tss file format.

1. I think .tss stands for "T-Spline Single". When exporting into this format, each T-Spline body of your model will be written into a single .tss file. There is also a .tsm file format, which I think stands for "T-Spline Multiple", it can store several T-Spline bodies at once. As this is a purely T-Spline specific file format, it doesn't support other file information.

2. You can save an .sf3d file with your canvas, and import it another file (instead of opening it).

3. I thought it would, but looks like I'm wrong. Doesn't seem to work for me, and I also couldn't find any indication in our database that there has been work on this, sorry.

Best regards,

Michael

Michael G.-G.
Manager Quality Assurance Automotive

jaihoyoo · ‎08-10-2016

Hi Michael

Thanks for the information.

Your answer to saving Canvas, it worked fine but I need to delete history to import form old file.

Otherwise I can see message telling that Canvas importing is not possible yet if there is timeline(?) in the file.

KR

Jay

Michael-GG · ‎08-11-2016

Hi Jay,

I wasn't aware of this restriction, I hope it's still a feasible workflow for you?

Best regards,

GG

Michael G.-G.
Manager Quality Assurance Automotive

jaihoyoo · ‎08-11-2016

Hi Michael

Yes it worked fine because it were all just images.

KR

Jay

dahem · ‎09-25-2016

Please can somebody help me and excuse me for posting my question here i couldn't find where else !

So the matter is i have speedform and autostudio 2016 student versions , when i export my work from speeform to autostudio , i can not see the hull even when i activate its button and i can not not select or edit anything curves or surfaces !

Michael-GG · ‎09-26-2016

Hi Dahem,

you should use the latest version of Speedform (2017), there it works autimatically. In your current version, you must go to "Edit - Ungroup" in Alias first before being able to activate the CV display.

Cheers,

GG

Michael G.-G.
Manager Quality Assurance Automotive

dahem · ‎09-28-2016

thanks a lot michael

i have done that but still nothing changed and apparently 2017 can not run on my pc it crashes everytime i try to run it... can you provide me any further help to work on the 2016 version

thanks

Michael-GG · ‎09-28-2016

Can you please send a CER (crash report), and let me know the number, so we can fix the crash?

As mentioned above, unstitching in Alias should work. Doesn't it?

EDIT: Sorry, you need to ungroup, then it should work?

Cheers,

GG

Michael G.-G.
Manager Quality Assurance Automotive

jaihoyoo · ‎09-28-2016

Hi Dahem

Sorry for the late reply. I was on my vacation for last week.
Well I think you might already have solved the problem with this Hull issue but I would like to leave short information on that in case you havent got the solution yet.
Firstly, I would listen to what Michael has wrote below about installing and working with latest version.
About your invisible Hull, that is because your data has been stitched together and it can be only grabbed when you pick them as an object not as a surfaces. So if that is the case then go to Alias 2017, Surface edit ) Unstitch and select the object. Then you will see massive group of CVs that belongs to each surface then now you can ungroup them, and edit them as a surface.
Hope this has helped your problem.

Kind Regards

Jaiho

dahem · ‎10-06-2016

i am back , so i have formatted my pc and installed windows 7 with the
latest drivers etc... i installed autostudio 2017 : autostudio and
speedform are working fine , but when it comes to Vred it crashes whenever
i import a project or even open the armchair or genesis examples.this is
crashing message
[image: Images intégrées 2]

this is the oppening screen.as you can see the scene does not appear and
the views cube is scrumbled
. [image: Images intégrées 1]
This the error repport code :
* CER_137221653*

so installed VRED 2016 and did not want to work too ! this the message it
shows to mee :

[image: Images intégrées 3]*

These are the crash details :

and i did not have any problem with VRED 2016 OR 2017 before , please help
me...

dahem · ‎10-06-2016

This are the crashing details :

OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1

000007FEDD038D13 (ig7icd64): (filename not available): DllMain

000007FEDD031C63 (ig7icd64): (filename not available): DllMain

000007FEDD031531 (ig7icd64): (filename not available): DllMain

000007FEDCFDC6D9 (ig7icd64): (filename not available): DllMain

000007FEDD270FC1 (ig7icd64): (filename not available): DllMain

000007FEEC2B03F2 (vrOpenSGExt): (filename not available): osg::Gradient2Background::clear

000007FEE902BA38 (vrKernel): (filename not available): vrOSGWidget::renderBackgroundOnly

000007FEE9028510 (vrKernel): (filename not available): vrOSGWidget::paintGLI

000007FEE9027C31 (vrKernel): (filename not available): vrOSGWidget::paintGL

000007FEE9027C0C (vrKernel): (filename not available): vrOSGWidget::paintEvent

00000000607F0B56 (QtGui4): (filename not available): QWidget::event

000000006E5B8BA6 (QtOpenGL4): (filename not available): QGLWidget::event

000007FEE9016D8B (vrKernel): (filename not available): vrOSGWidget::event

00000000607B2C66 (QtGui4): (filename not available): QApplicationPrivate::notify_helper

00000000607B2900 (QtGui4): (filename not available): QApplication::notify

000000013F4C76AA (VREDDesign): (filename not available): vrApplication::notify

00000000612AD76C (QtCore4): (filename not available): QCoreApplication::notifyInternal

00000000607F0072 (QtGui4): (filename not available): QWidgetPrivate::drawWidget

0000000060975781 (QtGui4): (filename not available): QWidgetPrivate::repaint_sys

0000000060801576 (QtGui4): (filename not available): QWidgetPrivate::syncBackingStore

00000000607F0EF5 (QtGui4): (filename not available): QWidget::event

000000006E5B8BA6 (QtOpenGL4): (filename not available): QGLWidget::event

000007FEE9016D8B (vrKernel): (filename not available): vrOSGWidget::event

00000000607B2C66 (QtGui4): (filename not available): QApplicationPrivate::notify_helper

00000000607B2900 (QtGui4): (filename not available): QApplication::notify

000000013F4C76AA (VREDDesign): (filename not available): vrApplication::notify

00000000612AD76C (QtCore4): (filename not available): QCoreApplication::notifyInternal

00000000612AF343 (QtCore4): (filename not available): QCoreApplicationPrivate::sendPostedEvents

00000000612D2D39 (QtCore4): (filename not available): QEventDispatcherWin32::processEvents

00000000778B9BD1 (USER32): (filename not available): TranslateMessageEx

00000000778B98DA (USER32): (filename not available): TranslateMessage

00000000612D2583 (QtCore4): (filename not available): QEventDispatcherWin32::processEvents

0000000060811155 (QtGui4): (filename not available): QApplicationPrivate::openPopup

00000000612AA6FC (QtCore4): (filename not available): QEventLoop::exec

0000000060BB56C1 (QtGui4): (filename not available): QDialog::exec

000007FEE4F42902 (vrCrashReport): (filename not available): vrCrashReport::sendFiles

000000013F4C50D2 (VREDDesign): (filename not available): __XceptFilter

000000013F4CD83E (VREDDesign): (filename not available): `vredLoop'::`1'::filt$0

000007FEF470F2CB (MSVCR120): (filename not available): _C_specific_handler

00000000779C9D0D (ntdll): (filename not available): RtlDecodePointer

00000000779B91AF (ntdll): (filename not available): RtlUnwindEx

00000000779F1278 (ntdll): (filename not available): KiUserExceptionDispatcher