Posts made by .del

@ferdinand Thank you so much for digging into this. I'll look at your example more and try quantitizing the numbers. In the meantime I had written a catch for the -1.1102230246251565e-16 to treat it as zero but it's probably not a very robust solution. I like your idea of rounding them off instead. I didn't fully understand what that number represented. I tried searching it but didn't get any useful results. I tried again today and now I see what it is. I must have had something else in my search field when I originally tried.

We have a script for creating atlases of textures and if the UV is outside of the bounds it gets placed incorrectly on the atlased texture. This new script is intended to catch those so they can be corrected before hand. I think rounding anything within two decimal places of zero will work for our needs.

Is there a way to change the tags for this this thread as it's not a bug report. I thought it was but it turns out it's not.

Thanks you for the help. It's greatly appreciated.

I've been able to confirm that if I take the suspect vertexes and change them from a value 1 to .99 and then change them back to 1 they no longer cause the problem.

Hi -

Thank you both for responding.

I searched my model group and found other models with vertexes at the bounding box corners and those did not get flagged by my script so your suggestion of a malformed UV or some sort of overflow might be what my issue is. The script also worked as expected on your plane.c4d file as well as a cube.

If the overflow value is consistent perhaps I can test for that and allow it to pass rather than flagging the model?

I'm attaching a scene file with two models made from the same template. Ones fails to pass the test while the other works. They are labeled accordingly.

I've also trimmed the script to focus on the bounding box part. It's not as elegant as yours by any means but I'm a self admitted butcher of code. Just trying to make tools to streamline our workflow. They aren't pretty but they help us get home at the end of the day and I'm appreciative that the sdk is available. Please keep that in mind as you stumble through my vomit pile of a script. My code is not Pythonic.

Thanks for looking at my stuff.

.del

import c4d
import os
import math


from c4d import gui
from c4d import Vector
from c4d import bitmaps
from copy import copy
from c4d.modules import bodypaint



#####





#Start the clean up tasks to prepare for exporting to the library.


doc.SetMode(c4d.Mmodel)

dObjects = doc.GetActiveObjects(c4d.GETACTIVEOBJECTFLAGS_SELECTIONORDER)
if dObjects == []:
    message = "You must select at least one object"
    c4d.gui.MessageDialog(message, c4d.GEMB_OK)
else:
    c4d.StatusSetSpin()
    c4d.StatusSetText("Running Python Script")

    isolate = False
    for obj in dObjects:
        if obj.CheckType(c4d.Opoint):

            ############################
            # check that UV is within bounds
            #
            uvTag = obj.GetTag(c4d.Tuvw)
            polyCount = obj.GetPolygonCount()
            polygons = obj.GetAllPolygons()

            for poly in range(polyCount):
                polygon = polygons[poly]
                data = uvTag.GetSlow(poly)
                print("poly" + str(poly) + str(data))
                if polygon.IsTriangle(): #if the poygon is a triangle instead of a quad we need to delete the 4th key as that position data is skewed and throwing a false positive.
                    del data['d']
                for vertex in data:
                    if data[vertex].x < 0 or data[vertex].x > 1:
                        print(data[vertex].x)

                    if data[vertex].y < 0 or data[vertex].y > 1:
                        print(str(poly) +" " +vertex)
                        print(data[vertex][1])
                        print(data)




c4d.StatusClear()

uv boundary testing.c4d

Hi -

I made a script that gets the vertex points of a UV and checks to see if they or within the 0,0 1,1 coordinate system. The script flags any vertex position less than 0 or greater than 1.

I print the output to the script manager identifying which polygon number it is as well as if it's the a, b, c, or d UV vertex. I also print out the full data dictionary for that polygon.

I have one model that is getting flagged by my script for having a vertex less than zero. As I was digging through my script and looking at the model with the Structure Manager pulled up I found an interesting thing. Any vertex that has a V value of 1 in the structure manager is coming through uvTag.GetSlow(poly) as a scientific notation value of -1.1102230246251565e-16. I am not seeing the same issue if the U value is equal to 1.

I took a screen shot of the Structure manager laid next to the python console so you can see what I mean.

Any ideas on how I can program around this?

Thanks,
.del

 ############################
            # check that UV is within bounds
            #
            uvTag = obj.GetTag(c4d.Tuvw)
            polyCount = obj.GetPolygonCount()
            polygons = obj.GetAllPolygons()

            for poly in range(polyCount):
                polygon = polygons[poly]
                data = uvTag.GetSlow(poly)#returns a dictionary {a: Vector( u, v, w), b: Vector( u, v, w), c: Vector( u, v, w), d: Vector( u, v, w)}
                #print("poly" + str(poly) + str(data))
                for vertex in data:
                    if data[vertex][0] < 0 or data[vertex][0] > 1:
                        print(data[vertex][0])

                    if data[vertex][1] < 0 or data[vertex][1] > 1:
                        print(str(poly) +" " +vertex)
                        print(data[vertex][1])
                        print(data)

Thanks Manuel. I was able to work that concept into the overall script.

Hi- I have a python script that adds projects to the render queue successfully but now I'd like to be able to enable the Team Render option for them. After reviewing the documentation I felt like BatchRender.SetUseNet(self, n, on) was going to be the answer but I havn't been able to get it to work.

In the main body of the script I set dBatch = c4d.documents.GetBatchRender().
Later in the script I call batchRender definition.

def batchRender(dFilePath, objName):
    dBatchCount = dBatch.GetElementCount() #number of items already in the batch render
    dBatchCount += 1
    dBatch.AddFile(dFilePath +"/" + objName + ".c4d", dBatchCount)
    ####enable Team Render for item
    dBatch.SetUseNet(dBatchCount,True)

The script doesn't return any errors but the Team Render box is never activated.

Any insight is appreciated.

Thanks,
.del

Thanks for looking at it Manuel. Sounds like your getting the same behavior I'm seeing.

I'll add something to my script to parse it out.

Thanks Manuel and Cairyn for taking time to help.

.del

I was able to get it working once I knew that I was supposed to be passing text and you were right that once I re-laucnhed R23 it cleared up the problem with the export working from the main menu. I wish I knew about the GitHub file sooner as it would have saved me some time. My script is an adaptation of an fbx exporter I had been using. At the time I created I couldn't find much on .obj exporting. These things are two years old and I'm just circling back to them as I start using R23.

Unfortunately I've come to find that the new exporter uses a file path in the .mtl file for the image whereas the previous versions did not. I'm not sure why the change was made but having a file path in there is throwing off the software that imports the .obj files. I don't see a way for me to set set a preference for it. I find myself falling back to R21 again until I can dig into the possibility of writing something to alter the .mtl file.

Well it looks like exporting an .obj isn't working for me at the moment anyway. The full scripts exports everything except the obj and when I try to use C4D's menu to export an .obj nothing happens either. No error message....nothing....no file...no lockup......nothing. I've submitted a support ticket. I'm not sure if it's script related or just a bug in R23. I'll have to fall back to R21 again so I can keep working.

Thanks for your help, that worked. I swear that the documentation and what the SDK expects changes every couple of years. Several years ago I'd try words and I'd be told to use numbers and now it seams as if numbers work for some things but words are required for others. It can be a bit confusing for me at times but at least I have a working script again.

Just to clarify, I always thought when the documentation showed 'Parameter Type: int' that it meant a number and the number was representative of the numerical position in the list. You mentioned "numeric value of the five options shows that they are between 4092 and 4096". Where did you find those numbers? I don't see that in the Python documentation.

thanks,
.del

I'm using a 1 because it's the second value in the list much like I'm using for for Scale and Material where the numbers represent their positions in the list.

I'll give it a try with the value instead.

I just switched to R23 and am fixing some my python scripts. I'm running into an issue setting an OBJ Export Option. In particular it's something that I think is new - OBJEXPORTOPTIONS_EXPORT_UVS. In the documentation it looks like I should be setting it to a number.

Parameter: UVs

Parameter ID: c4d.OBJEXPORTOPTIONS_EXPORT_UVS

Parameter Type: int

Cycle Values:

        None (c4d.OBJEXPORTOPTIONS_UV_NONE)

        Original (c4d.OBJEXPORTOPTIONS_UV_ORIGINAL)

        Flip U (c4d.OBJEXPORTOPTIONS_FLIP_U)

        Flip V (c4d.OBJEXPORTOPTIONS_FLIP_V)

        Flip UV (c4d.OBJEXPORTOPTIONS_FLIP_UV)

Based on the documentation I think I should have something like this - objExport[c4d.OBJEXPORTOPTIONS_EXPORT_UVS] = 1 but it's throwing an error in the console 'AttributeError: parameter set failed'

Here's my block of code for this -

    #set up obj exporter

    plug = plugins.FindPlugin(1030178, c4d.PLUGINTYPE_SCENESAVER)
    if plug is None:
        print ("noPlug")

    op = {} # create dictionary to store key
    # Send MSG_RETRIEVEPRIVATEDATA to fbx export plugin
    if plug.Message(c4d.MSG_RETRIEVEPRIVATEDATA, op):
        # BaseList2D object stored in "imexporter" key hold the settings
        objExport = op["imexporter"]
        # Define the settings
        objExport[c4d.OBJEXPORTOPTIONS_SCALE] = 1
        objExport[c4d.OBJEXPORTOPTIONS_MATERIAL] =  2
        objExport[c4d.OBJEXPORTOPTIONS_INVERT_TRANSPARENCY] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_FLIPX] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_FLIPY] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_FLIPZ] = True
        objExport[c4d.OBJEXPORTOPTIONS_FLIPFACES] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_SWAPXY] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_SWAPXZ] = False
        objExport[c4d.OBJEXPORTOPTIONS_POINTTRANSFORM_SWAPYZ] = False
        objExport[c4d.OBJEXPORTOPTIONS_EXPORT_UVS] = 1
        objExport[c4d.OBJEXPORTOPTIONS_OBJECTS_AS_GROUPS] = False
        objExport[c4d.OBJEXPORTOPTIONS_TRIANGULATE_NGONS] = True

Is anybody else running into this or am I missing something on how to set the UV parameter of the export?

Any help is appreciated.

found it!!! I had to float('0.5')

Does anybody know what format I'm supposed to use to send a number to the Bevel tool for the radius? I'm currently only able to get it to work with whole numbers like 1 or 2. I'd like to set it to .5.

I've tried float(.5) and int(.5) but both end up giving me no bevel. I can't find any documentation for this.

thanks,
.del

Restarting c4d fixed it! Now I just have to get the hidden polys produced by the bevel to appear. I'm pretty sure I need a message update or something like that as they appear once I move the model.

Thanks for your help.
.del

C4D might have been 'messed up' based on my prior attempts. I've restarted it and may be making progress.

Hi and thanks for the help.

I tried the script but I don't get any results. No error message and no change to the model. Please keep in mind that I'm in R19 if that makes a difference. I tried it in R20 and it creates a bevel. Not the bevel I expected but it was at least promising that it did something.

Here is what I have based on your info.

import c4d
from c4d import utils

def main():
    bcBevel = c4d.BaseContainer()
    bcBevel[c4d.MDATA_BEVEL_MASTER_MODE] = c4d.MDATA_BEVEL_MASTER_MODE_CHAMFER
    bcBevel[c4d.MDATA_BEVEL_OFFSET_MODE] = c4d.MDATA_BEVEL_OFFSET_MODE_FIXED
    bcBevel[c4d.MDATA_BEVEL_RADIUS] = 1
    bcBevel[c4d.MDATA_BEVEL_SUB] = 2
    bcBevel[c4d.MDATA_BEVEL_DEPTH] = 1
    bcBevel[c4d.MDATA_BEVEL_SELECTION_PHONG_BREAK] = False
    
    
    tags = op.GetTags()
    
    for tag in tags:

        if tag.GetType()==5701:
            doc.StartUndo()
            doc.SetMode(c4d.Medges)
            selection = tag.GetBaseSelect()
            edgeSelected = op.GetEdgeS()
            selection.CopyTo(edgeSelected)
            doc.AddUndo(c4d.UNDOTYPE_CHANGE, op)
            res = c4d.utils.SendModelingCommand( c4d.ID_XBEVELTOOL, [op], c4d.MODELINGCOMMANDMODE_EDGESELECTION, bcBevel, doc)
            doc.EndUndo()
            c4d.EventAdd() 

if __name__=='__main__':

    main()

Just when I thought I might be getting the hang of python in C4D I ran into a challenge of trying to bevel an edge selection. I've been able to piece together most of what I think I need but I've run into two problems. The first being that I can't set the offset of the tool and second I must be missing some sort of command to have the polygons show up after the resulting bevel takes place. I've been scouring the forums and trying a bunch of things for the last few hours and I've come to the point where I have to throw in the towel and seek professional help.

Any and all help is appreciated.

Here's what I have so far -

tags = op.GetTags()

for tag in tags:
    if tag.GetType()==5701: #edge selection
        doc.SetMode(c4d.Medges)
        selection = tag.GetBaseSelect()
        edgeSelected = op.GetEdgeS()
        selection.CopyTo(edgeSelected)

        c4d.CallCommand(431000015,431000015) # xll bevel tool
        tool = plugins.FindPlugin(doc.GetAction(), c4d.PLUGINTYPE_TOOL)
        bcBevel =  doc.GetActiveToolData()
        bcBevel.SetData(c4d.MDATA_BEVEL_OFFSET_MODE, 0)
        bcBevel.SetData(c4d.MDATA_BEVEL_RADIUS, 1)
        bcBevel.SetData(c4d.MDATA_BEVEL_SUB, 2)
        bcBevel.SetData(c4d.MDATA_BEVEL_DEPTH, 1)
        bcBevel.SetData(c4d.MDATA_BEVEL_SELECTION_PHONG_BREAK, False)
        c4d.CallButton(tool, c4d.MDATA_APPLY)
                                       
op.Message(c4d.MSG_UPDATE)            

c4d.EventAdd()

Problem was with the total path length versus the file name length. 256 characters for the entire path and filename.

Hi -
I switched from Mac to Windows a few months back and am now experiencing a problem with one of my scripts. I'm using SaveDocument() to create some individual files from the models in my main document. The script isn't necessarily failing but I'm getting a alert that my export has failed. The best that I can come up with is that I'm running into a 64 character limit on the filename on Windows. I've taken a test model and re-worked it's name and 64 characters exports but 65 and longer do not.

I do believe that there was a time when that was a thing but the current OS supports longer filenames. Can you please confirm if it's a limitation in the sdk? or maybe it's a python problem? Either way I'm just looking for some confirmation so I can stop beating my head against the wall.

Thank You