43 replies to this topic

[wailingmonkey]

Are you running 2.10.10 ?

indeed... if it's of any importance or bearing, I've got .NET 2.0 installed on my desktop (not
sure which on the laptop)

perhaps someone else can test it too?
(can't imagine I've managed to screw up your install instructions that badly)

[JamesH]

indeed... if it's of any importance or bearing, I've got .NET 2.0 installed on my desktop (not
sure which on the laptop)

perhaps someone else can test it too?
(can't imagine I've managed to screw up your install instructions that badly)

In the root folder there should be a file named Log.txt, can you have a look for the three entries

cMeshIO::AddCodec(): Added "Obj" mesh codec.
cMeshIO::AddCodec(): Added "Lwo" mesh codec.
cMeshIO::AddCodec(): Added "Fbx" mesh codec.

And there should be one just before that reads if the plug-in is being loaded

cMeshIO::AddCodec(): Added "dae" mesh codec.

[wailingmonkey]

doesn't seem to be loading properly for me...the entry before those three is: Loaded image file "textures\vista3.dds"
(I can't find 'cMeshIO::AddCodec(): Added "dae" mesh codec.' in the text file)

anything hard-coded in the .dll in terms of paths? (cause I've installed 3dC into a c:\graphics\3d-Coat-2-10 path)

gonna sleep now, but I'll test more tomorrow.

[JamesH]

doesn't seem to be loading properly for me...the entry before those three is: Loaded image file "textures\vista3.dds"
(I can't find 'cMeshIO::AddCodec(): Added "dae" mesh codec.' in the text file)

anything hard-coded in the .dll in terms of paths? (cause I've installed 3dC into a c:\graphics\3d-Coat-2-10 path)

gonna sleep now, but I'll test more tomorrow.

There's nothing hardcoded, and I've just uninstalled and re-installed into a similar location and it works fine.

Incidentally, what OS are you using ? I'm running XP SP2 and XP SP3 on my dev machines, I have another with Vista that I can try tonight to see if I can reproduce your problem.

Has anyone else tried the plug-in ?

Cheers.

[Andrew Shpagin]

It works well on last ALPHA. It creates DAE file with reference to texture.
Is there some viewer to look it rendered?
Is it possible to export with normalmap? I see it is referred in DAE file, but will it be accepted by external render?

[JamesH]

It works well on last ALPHA. It creates DAE file with reference to texture.
Is there some viewer to look it rendered?
Is it possible to export with normalmap? I see it is referred in DAE file, but will it be accepted by external render?

I've got the Normal map included for the next build which I'll release tonight.

Try COLLADA Loader to view the file.

Cheers

James.

[Andrew Shpagin]

I've got the Normal map included for the next build which I'll release tonight.

Try COLLADA Loader to view the file.

Cheers

James.

Exported files look fine with that viewer.

[JamesH]

Exported files look fine with that viewer.

Thanks, and I've just updated the download to reference the normal map.

[Andrew Shpagin]

Thanks, and I've just updated the download to reference the normal map.

That viewer does not show normals... But I see changes in file structure.

[wailingmonkey]

bizarre...still won't show up with Alpha18 (doesn't initiate in log.txt either).

I'm running XP SP2 (32-bit) and here's where I've got the .dll:

Attached Thumbnails

• 

[JamesH]

bizarre...still won't show up with Alpha18 (doesn't initiate in log.txt either).

I'm running XP SP2 (32-bit) and here's where I've got the .dll:

I've got an old build of the Alpha that it doesn't show up in, I'll get the latest version and have a look.

Does it work with 2.10.10 ? If not, can you also try disabling your virus scanner when running 3DC (wild stab in the dark, but the scanner could be scanning the .dll as it's loaded and locking it).

[wailingmonkey]

doesn't run with 2.10.10 either (and no-show in log.txt). no virus scanner when running 3dc, so that doesn't
appear to be it either...

I'll try it on my laptop with 3.0 alpha in a bit, but won't be able to check back in till later this evening.

Seems really strange that it's not being picked up by Windows as an optional pulldown (since you can see
I haven't bungled placing the .dll in the appropriate folder )

[JamesH]

doesn't run with 2.10.10 either (and no-show in log.txt). no virus scanner when running 3dc, so that doesn't
appear to be it either...

I'll try it on my laptop with 3.0 alpha in a bit, but won't be able to check back in till later this evening.

Seems really strange that it's not being picked up by Windows as an optional pulldown (since you can see
I haven't bungled placing the .dll in the appropriate folder )

I'm out of ideas I'm afraid, it works on Alpha18 for me as well.

Andrew, have you got an idea on the problem ?

EDIT : Andrew would the VS2005 Redistributable Package be needed ? I don't know about this, but the common denominator on both my machines is VS2005 - only a thought.

[wailingmonkey]

just to make sure I could operate with .dae, I took my test object I gave you into Ultimate Unwrap 3d and
saved it out as .dae ... and then re-imported it back into UU3d as .dae (and it retained all properties of its
original .obj format)

I'm outta ideas too, sadly ... hopefully others won't run into this problem if they need .dae <shrugs>


*edit* Just installed the 2005 visual c++ redistributable and re-booted, but still no-go for both 2.10.10 or
3.0alpha18 .... pulldown option on export just shows .lwo and .obj

[Andrew Shpagin]

I have looked dll's contence and it refers to

MSVCP90.dll
MSVCR90.dll

It seems DLL is compiled and MFC libraries are not linked statically. JamesH, please check it in options.

[JamesH]

I have looked dll's contence and it refers to

MSVCP90.dll
MSVCR90.dll

It seems DLL is compiled and MFC libraries are not linked statically. JamesH, please check it in options.

Not really knowing too much about this topic, I recompiled using the /MT option and checked the .dll with DependencyWalker and it seems to be ok now - is there anything more for me to do ?

I've uploaded a new build.

[Andrew Shpagin]

Not really knowing too much about this topic, I recompiled using the /MT option and checked the .dll with DependencyWalker and it seems to be ok now - is there anything more for me to do ?

I've uploaded a new build.

I have checked - it does not depends on VS DLL-s now.
It is interesting, have you succeed with normalmap exporting and rendereing?

[JamesH]

I have checked - it does not depends on VS DLL-s now.
It is interesting, have you succeed with normalmap exporting and rendereing?

To be honest the only package I have that can display the normal maps is C4 and the normal map imports fine into it, I used the <bump> element tag to identify the normal map texture. Although that tag isn't listed in the COLLADA spec and after going through a lot of the COLLADA examples it's a bit vague on identifying what the normal map references need to be. Each package seems to use a slightly different way to identify actual textures. I'm going to have a look this weekend and maybe post on the COLLADA forums so that I can get a definitive answer.

[JamesH]

In fact the bump extension is not supported by 1.4.1 or 1.5 and is discussed here, but it has been added as part of the Max extensions in the COLLADAMAx exporter from FeelingSoft, discussed here.

[wailingmonkey]

thanks Andrew and JamesH, the dependence on those MSVC .dll seems to have been the issue.

I'm now able to see the .dae option (and consequently export, woohoo!)