[zoetropeuk]

I know I'll probably get banned for this but enough is enough.

The current C4D plug-in would have to be the biggest piece of crap software I've ever had the privilege of using. Maybe PC users are used to really, really bad software but I just can't fathom how this gets released.

The beta testers, if they exist need to pull their heads of out their collective behinds and TEST THE F@CKING software. Even simple things DO NOT WORK, do I need to repeat that ?

Here is my list of features that DO NOT WORK. I don't care if NL or the A-Team think they work because they DON'T:

1. Textures and UV mapping DOES NOT WORK.
2. Custom MXM textures STOP WORKING, so they DO NOT WORK
3. The Sky Map tag DOES NOTHING, I repeat NOTHING
4. The polygon selection tag DOES NOT WORK

I could add more but even at point 1 it's a useless piece of crap.

Matt

[Tyrone Marshall]

Thanks for the information.

[zoetropeuk]

I better elaborate otherwise NL with think I'm just stirring trouble.

1. The scale and rotation of the images maps are incorrect when opened in Studio. I need to rotate all images map 90º and scale on one axis by a factor of 10. Why is this ? And yes, I've tried reseting the co-ordinate system in C4D and every other option I can think of.

2. For some reason something I've changed in my C4D file stops the custom MXMs from working properly. I have a black anodise type material that now looks like aluminium. It doesn't matter what I try, delete, reset-up, the scene no longer renders properly.

3. This is self explanatory. At least in version 1.0, 3 of the channels were transferred. Now nothing happens, you may as well just delete it from list of tags as it just wastes peoples time

4. Again, whoever programmed this needs a kick in the head, what's the point in having to separate the polygons as selections ? Once you've done this you don't need to use a selection tag anyway And the limit of one MR tag per object is just stupid.

5. If I have a bump map in an MXM then it's used as the colour/texture map and overrides the other layers or texture parameters

These workarounds are obviously thrown together at the last minute to buy NL some more time.

Could someone from NL please share their testing methodologies for the C4D plug-in ? Do you have a set of standard scenes that you render to verify the functionality of the current version. Or do you just close your eyes and upload whatever is ready ?

I think the only solution is to fire the current plug-in developer, get rid of the A-team members and release daily updates for current owners to test. I'd guarantee you that the plug-in would be years ahead if you did this from the start. You'll probably say that this won't work but the situation couldn't be much worse

Matt