Leaderboard
-
in File Comments
- All areas
- Videos
- Video Comments
- Files
- File Comments
- File Reviews
- Pipelines Tools
- Pipeline Tool Comments
- Pipeline Tool Reviews
- Databases
- Database Comments
- Database Reviews
- Plugins
- Plugin Comments
- Plugin Reviews
- Images
- Image Comments
- Image Reviews
- Albums
- Album Comments
- Album Reviews
- Topics
- Posts
- Blog Entries
- Blog Comments
- Status Updates
- Status Replies
-
All time
-
All time
May 3 2016 - March 28 2024
-
Year
March 28 2023 - March 28 2024
-
Month
February 28 2024 - March 28 2024
-
Week
March 21 2024 - March 28 2024
-
Today
March 28 2024
- Custom Date
-
All time
Popular Content
Showing content with the highest reputation since 05/03/2016 in File Comments
-
The new "Store Selection" uses the same command ID as the old "Set Selection". My guess is that MAXON has simply renamed and reimplemented the old command with the new behaviour. I have provided here a script which mimics the old behaviour. Have not tested on S24 or above. Enjoy! Set Selection (legacy).zip2 points
-
2 points
-
Next to adding support for R25, and fixing bugs, I have also added some extra options to show a tool-tip when hovering over an item. I have also added some background behind the items in the main dial to provide for some contrast. All configurable with additional options. However, I have mainly focused on developing for R20 as this is the version I am mainly using. I know the color scheme in R21, and especially R25, are darker than R20. The default values I thus have provided might not match those newer versions. Feel free to set up your own background color and opacity, as well as the tool-tip background color, and text color, font size, ... etc.2 points
-
2 points
-
1 point
-
Finally! Whole thing bothered me quite a while now, but I'm quite certain now: We're using Corona Render including Corona Sky. It seems like the material that appears after I click your script is the internal material for the Corona Sky object. After the material is visible, I can change something inside the Corona Sky object and the changes also happen inside the material. When I delete the material, the viewport background changes and the sky disappears. Looks like the material is solely for the viewport background, because the rendering still works - it is only affecting the viewport. Quite funny: 'Delete Unused Materials' deletes the material too and the background disappears. Adding a new Corona Sky works and the sky is visible again ... I guess your script digs a little too deep into the material hole in that case. Nothing is lost there, but I imagine it could be frustrating if you don't know what is going on. I've created a new comment in case someone else is looking for that behavior1 point
-
1 point
-
1 point
-
1 point
-
Hey Unfortunatelly i noticed that Maxon changed the order of some icons and deleted its path. Some new icons like the animation tag are above old ones so there is no way to replace it unless i change the new version. This was a quick fix in order to re-establish the viewport/ curve editor icons , etc and other that i really need and were gone. This "mix" is meant to help during the transition to the new c4d without causing chaos. Fixing the txt file was the real deal in order to achieve this. cheers1 point
-
1 point
-
1 point
-
1 point
-
@dast Oh god, i never saw that documentation... I was so excited cause i found the plugin after a long time. Anyway, the fault was on my end, nothing wrong with the plugin. I just thought that it would work like other plugins by placing it at the installation folder instead of the preferences one... Then i copied it to the preferences and just forgot to remove it from the installation one... Yeah i know, but like i said i was so excited Thanks again dast, it's an amazing plugin!!! @bezoAnd of course, thank you for the help, without you i would still try to figure out what's wrong1 point
-
Glad it worked out for you. However, the plugin contains documentation that describes how and where to install the plugin, depending the version of Cinema4D you are using. What was the reason that made you decide to install in both folders? Knowing why might help in provide better and more accurate documentation in the future.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
Man! This is so embarrassing ... I never realized I hadn't completed the functionality for points and edges. Up to now I only needed the script for polygon selections, and all was fine. The other day I needed to create edge and point selection ... and nothing worked. Whaaat !? Uploaded version 1.2 with completed functionality for polygons, edges, points. There you go! Sorry for the inconvenience. Soooo embarrassing!1 point
-
1 point
-
1 point
-
1 point
-
New version 0.2 has been uploaded, which should solve all issues mentioned above (see also the Details tab, for more info) Since different version of Cinema4D have different Material Manager menu I have decided to simply append a Search menu item at the end of the existing menu, instead of trying to insert it into an existing one. As this would clash with other plugins adjusting these menus as well. I have also added a toggle button, which allows to show or hide the materials that match the entered text. Big thanks to user bezo for beta-testing the latest version.1 point
-
1 point
-
1 point
-
1 point
-
Thanks for the feedback! You are correct. I missed testing the plugin with lower and uppercase. My bad. However, I don't see the point in providing a preference for this. I assume that making it case insensitive would be good enough. Version 0.2 will have this update, but I am waiting for some more feedback before releasing the update, as I am sure I must have overlooked other minor but obvious annoyances.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
If you see the welcome message of a plugin 3 times in a row then there definitely is something wrong with your install. Unless you have installed the plugin in 3 different folder locations. Which you shouldn't do since then the different plugin instances will clash with each other. But in your case, only having the plugin installed in one location will not work either, as the welcome message clearly states you're running an unsupported version.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
2 ... and all the other ones! This script has now been updated to be compatible with Python 3.7, which is used in R23. Note that next time you have a problem, it would be handy to copy the error from the console and paste it here. This would allow to investigate the issue. It seems this was a quick fix, as the "print" command in Python 3.7 requires parenthesis. No other changes required. Enjoy the update!1 point
-
This remark would better fit in the appropriate topic: the Points2Circle download section. There you can find the updated script. The original one was written in Python 2, which is used in Cinema4D prior R23. While R23 uses Python 3. Since both aren't 100% compatible the original script had to (very slightly) be adjusted to work with Python 3. Note that the new upload is still "pending for approval" ... it might take a while before the updated script becomes available.1 point
-
1 point