Hello, there is no thing as mouse direction. The mouse has a position. The direction is the result of comparing two mouse positions. as @zipit stated, you can create a tool that implements MouseInput(). Within MouseInput() you can use ViewportSelect.PickObject() to check what object and what point the mouse is currently over (Using BaseView.SW()). You can store the previous mouse position and compare it to the current mouse position to calculate the direction. Unfortunately, there is an issue with the Python version of PickObject() (How do I find the z-depth with Python ViewportSelect.PickObject()?), so you might have to implement your idea as a C++ plugin. You find some code in the pickobject.cpp example. best wishes, Sebastian

Hello Sebastian, thanks for this quick response! I dind't know about this. But this solved my issue! Best Regards, Florian

@r_gigante Yes! It's really helpful.

Here's a dump from DxDiag: ------------------ System Information ------------------ Time of this report: 9/19/2019, 21:45:45 Machine name: NUC Operating System: Windows 10 Pro 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202) Language: English (Regional Setting: English) System Manufacturer: Intel(R) Client Systems System Model: NUC8i5BEH BIOS: BECFL357.86A.0064.2019.0213.1122 (type: UEFI) Processor: Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz (8 CPUs), ~2.3GHz Memory: 32768MB RAM Available OS Memory: 32636MB RAM Page File: 2894MB used, 34606MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: Unknown DxDiag Version: 10.00.18362.0267 64bit Unicode --------------- Display Devices --------------- Card name: Intel(R) Iris(R) Plus Graphics 655 Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Plus Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_3EA5&SUBSYS_20748086&REV_01 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 16446 MB Dedicated Memory: 128 MB Shared Memory: 16318 MB Current Mode: 1920 x 1200 (32 bit) (59Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.673828,0.319336), Green(0.187500,0.706055), Blue(0.148438,0.064453), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: DELL 2408WFP Monitor Id: DELA02C Native Mode: 1920 x 1200(p) (59.950Hz) Output Type: HDMI Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_bf9afe57cbde0e11\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_bf9afe57cbde0e11\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_bf9afe57cbde0e11\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_bf9afe57cbde0e11\igd12umd64.dll Driver File Version: 26.20.0100.6912 (English) Driver Version: 26.20.100.6912 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.6 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 28/05/2019 02:00:00, 1887728 bytes WHQL Logo`d: n/a WHQL Date Stamp: n/a Device Identifier: {D7B78E66-7DE5-11CF-36F8-1000BAC2D735} Vendor ID: 0x8086 Device ID: 0x3EA5 SubSys ID: 0x20748086 Revision ID: 0x0001 Driver Strong Name: oem4.inf:5f63e5341264f0f6:iCFL_w10_DS:26.20.100.6912:PCI\VEN_8086&DEV_3EA5 Extra note: I now only have the included plugin projects in the solution, and use cinem4dsdk as startup project. No other plugins of mine are part of the solution. This whole issue reminds me about this: https://plugincafe.maxon.net/topic/11212/memory-leak-after-plugin-migration-r16-r20 Same situation, memory leaks not reproducible.

hi, sorry for the delay of this answer ... Well, as you understood, you can't have a spline with open and closed segments. It's global for the entire spline, either all closed or all opened. The parameter is there, in the structure. It's sometimes used internally instead of the spline parameter. Cheers, Manuel

@m_adam said in [python] SetFont not working: In which version are you? The code I posted is working nicely in R20.059. 20.059. Before i tried any methods, that's my fail. Not work for me. From new start of c4d. - it works

Hello, Sorry for the delay. The bugs have been confirmed and will be fixed on a futur release. Cheers Manuel

hello, we did run a couple of test and seems that the "issue" is on Patreon side. HTTP Error 403: Forbidden We did try with other url, it work. We did try adding header-agent or things like that, it failed. They probably changed something on their server that doesn't allow to connect with python with default parameters. You have to contact them in order to know what you have to do. Cheers Manuel

Hi Root Star, thanks for reaching out us. With regard to the IDE version, we highly suggest sticking the compatibility table reported in our documentation. Visual Studio 2019 is not supported by R20 and it's likely not to be officially supported also on R21. With regard to .hxx files, these are generated by our source processor when the building process is initiated and it's highly discouraged to change or get rid of them during the building process. The issues you're facing are highly related to the fact that the solution/project file(s) built by the projecttool (when kernel_app_64bit.exe g_updateProject=<your path to Cinema SDK> is executed) are not 100% compatible with VS2019 resulting in building tool-chain flaws. Best, Riccardo

Hi Manuel, Right! Found the culprit... symbolcache file... Couldn't understand how it was working for you and not for me. After deleting symbolcache worked straight away and it seems that also works without having doc.SetActiveTag(outro_cal_tag) Thank you very much for your awesome help with this! Andre

@m_magalhaes Thanks, hope to fix it in a future release.

hello, we are sorry to hear that. Unfortunately this forum is for maxon API support and for every thirds party developers. Your issue look like a bug or something, you have to use this platform instead side remark : As this is your first post i would also like to point you to this topic I've set this up this time but it is important, that will help us and the community. Cheers Manuel

Again sorry, I've tested with the Studio version. Using C4DPL_PROGRAM_STARTED case I can confirm this "bug" with a Educational version and a Demo version. Not with the Studio version. Maybe something with that extra "popup" windows on those both versions. Cheers Manuel.

I understand, that makes sense to me. Thank you for the help. Dan

Don't feel sorry yes this is the issue and since Knot ID are not ordered from right to left but from creation order its why it's confused you. Moreover, using a for loop will make way more sense and help you to avoid this kind of stuff. grad1 = shdr1[c4d.SLA_GRADIENT_GRADIENT] grad2 = shdr2[c4d.SLA_GRADIENT_GRADIENT] for knotId in xrange(grad1.GetKnotCount()): knot = grad1.GetKnot(knotId) grad2.InsertKnot(col=knot['col'], pos=knot['pos'],index=knot['index']) grad2.FlushKnots() shdr2[c4d.SLA_GRADIENT_GRADIENT] = grad2 Finally, a BaseShader is derived from BaseList2D which is derived from C4DAtom that mean you can use GetClone to retrieves a clone of this shader so your code can look like. import c4d def main(): mat = doc.GetFirstMaterial() colorShader = mat[c4d.MATERIAL_COLOR_SHADER] if colorShader is None: return copyColor = colorShader.GetClone() mat[c4d.MATERIAL_DIFFUSION_SHADER] = copyColor mat.InsertShader(copyColor) mat.Message(c4d.MSG_UPDATE) mat.Update(True, True) c4d.EventAdd() # Execute main() if __name__=='__main__': main() Cheers, Maxime.

Thanks Sebastian! Looking forward for a fix. ;) Meanwhile I'll take care of your recommendation. Best, Robert

Hi Daniel, I filed a bug report with regard to this unexpected behavior. I will keep you updated on resolution. Best, Riccardo

Hi, thanks for pointing this out to us. Yet, we were not able to reproduce this issue. What we found so far, when doing a search for "EventAdd()" (or anything similar resulting in a large number of results) and the search is set to show posts instead of threads, then switching between result pages can indeed take some time (at least for the first switch). During this time the page is indeed completely unresponsive and seems frozen, which is not nice. But here it always returned and showed the expected content after a bunch of seconds (I think in my tests longest was about 15 seconds). We'll keep an eye on this. Cheers, Andreas

Hi @Fransua welcome in the plugincafe community. Do not worry since it's your first post but please read and follow these rules (I've setup your post correctly) How to Post Questions especially the tagging part. Q&A New Functionality. Unfortunately, a complete list is not available for the moment. But if you are looking only for object there is this page Object Types and Fields Object Types which refer to all symbols available to describe an object. To know a specific object id, you can drag and drop this object/element to the console, for more information see Python Console, Scene Elements. Finally, you can also retrieve for the full list of id by their type with c4d.plugins.FilterPluginList Cheers, Maxime.

@a_block Hi Andreas, Thanks for your help and you are never too late! That actually makes more sense. Unfortunately I can't seem to replicate the issue again on my machine, as it seems that it's been working for all my updates. I will have a look on one of my team machines when released and see if that could be the problem. Thank you again!