search

awaytools / AwayExtensions-C4D

15 stars 5 forks source link

Issue with 'none' texture #1

Closed Sean72 closed 10 years ago

Sean72 commented 11 years ago

In an early version of the exporter, there was an issue during the convert stage with the export process stopping partway because it could not locate a texture. The missing texture is given as ...\tex\None. The error says 'Invalid Object'.

The issue was discussed here http://away3d.com/forum/viewreply/13196/

This problem was fixed in the AWDBridge version with files dated Monday, ‎April ‎01, ‎2013, ‏‎5:07:56 PM. However, it has cropped back up again in the current version.

I checked all my materials, but the 'color' channel textures are all fine and the previous plugin exports the file successfully.

I then looked in the other channels of the materials and on one of them, I found that 'diffusion' and 'reflection' had noise and fresnel as textures. When these were cleared, the error no longer showed up, but the exporter stopped early at 21% and then said 'ready' as per the screen capture below, but with the all the files still renamed as numbers and no file generated.

Anyway, I can workaround it by rolling back to the previous version, but wanted to share this so it can be fixed.

I will say, thanks for developing an awesome plug-in for Cinema 4D! This bridge has made my work with Away3D better and easier.

Sean72

moz-screenshot-12

Sean72 commented 11 years ago

UPDATE: I tried deleting all materials and the exporter started and quite almost instantly, again with all objects renamed to numbers, no error message. So I think this might be a second bug. Something in the file that exported before just fine is not causing the plugin to crash. If I can help further, e.g. by creating a debug log or trying to narrow down the object(s) causing the crash, please advise.

80prozent commented 11 years ago

Hey sorry - didnt got email-notice about issues here - will look into this asap (in the middle of refactoring the plugin to work with the new ppyawd, so i hope this issue will be solved anyway with the next update...)

Sean72 commented 11 years ago

No problem, I have a workaround meanwhile.

Sent from my iPad

On Aug 17, 2013, at 10:35 PM, Robin Lockhart notifications@github.com wrote:

Hey sorry - didnt got email-notice about issues here - will look into this asap (in the middle of refactoring the plugin to work with the new ppyawd, so i hope this issue will be solved anyway with the next update...)

— Reply to this email directly or view it on GitHub.