dast

This is by design. When you haven't switched to another tool you need to press the "New transform" button in the Attribute Manager to trigger a new extrude. Otherwise you keep adjusting the last made extrusion.

First beta of bridging PolyDup and PolyGnome is in process of being completed. A short video demonstration the workflow: @3D-Pangelinterested in beta-testing this update for both plugins?

It took some time, but I am in the process of building a "bridge" between PolyGnome and PolyDup. I would like to be able to send objects from PolyDup's slots to PolyGnome's library ... and vice versa. It is still early in the process, but right now I have a working concept to retrieve PolyDup's extracts from within PolyGnome's Junkyard dialog, and stored it in the library. What is still left to do is get some thumbnail generated. So, expect some updates on these plugins in the near future.

Reconsidering, I have updated the plugin to version 1.4. Having taken the opportunity to setup a building environment for R23 and S24 on Windows and macOS. This is becoming quite a hassle. Which reminded me of one of the reasons having contributed to quit the plugin-business. The plugin(s) is available in the download section.

The top parent of the eyes are set to be hidden (the top "traffic" light is set to red for "Root_con+" in the object manager). Since the eyes are now child of this, they inherit the state, and thus are hidden. You can set the eyes top traffic light to green, and it will override the parent's hidden state. Just click once on the top dot to turn it green.

Good afternoon as well. I stopped selling my plugins a while ago. You might find some more info in following topic. https://www.core4d.com/ipb/forums/topic/112141-polydup-and-a-50-off-sale I have been looking into providing some of my plugins as downloadables here (see EasyUV as a first step into that direction). But due to lack of interest - and feedback - I am not sure I still want to put time and effort into this.

Not sure if exporting would be the solution, but it sure is a nice idea to try and collect as much info regarding as many workflows as possible. Some may not see the need, and I agree that the current community is mostly C4D orientated. But if possible workflows are presented and explained, it might lead to more and more people trying out and adapting workflows to their own need. The main problem is we need pioneers who know what they're doing to get things started ... and be able to explain to the less techy-minded (myself included) how to go about. Unfortunately, I seem to have noticed that the community as a whole, with exception of a few die-hards, is becoming less and less involved in providing feedback. Most people here seem to look for an answer, to never be seen again when their question gets answered. Some even aren't seen again right after having posted their question.

Yeah, not sure what to think of this. Only marketing in the hopes of getting something bigger out of it. Or are they trying to get a foot in the door and make Blender follow the footsteps of Substance Painter? Sometimes people start to get really paranoid. Me included.

Same here. I was about to finally dive into the world of GPU rendering (when I get my hands on a RTX GPU) and was looking to purchase a perpetual license of Redshift, Octane, or both. Recently was pointed in another discussion to the fact that Corona render would be a nice CPU-only alternative. But as that is subscription only it doesn't fit my budget. And now with Redshift going subscription only ... that's another one I can remove from my want-to list. Octane and U-Render seem to be the only candidates left. Unless they go subscription-only as well ...

Not owning a GPU I had been waiting to get an RTX 3070 (when prices are "fair" again) and been on the lookout for either Redshift, Octane or both. But as perpetual license, not subscription. Not sure what to do now, but it seems the dilemma to choose Redshift, Octane or both has clearly resolved itself by the time I will be buying an RTX. That is unless Octane also goes subscription only ... Well, if all decent renderes are going subscription only it's bye bye 3D hobby for me ... or stick with the current Physical ... or step over to Blender.

I meant "an option to buy a perpetual license of Corona render for C4D" ... but I see where my original message might have mislead you. The fact is that there is an option to buy the perpetual license (of Corona render 😉 ) for 3ds Max, just not for C4D ... hence the question. Thanks.

Do you have a perpetual license or subscription? Just wondering, as I don't see an option to buy a perpetual license for C4D anymore.

My plugins are not available for purchase anymore. Please read the first post of this topic. There you will find out the differences between EasyUV and Seamilar. The first post also mentions you can find EasyUV in the downloads section.

As mentioned in the first post the plugin only works in R16 upto R21. Does not work in S22, R23, S24, ...

As I haven't updated the documentation yet I have added 2 more demonstration videos to the first post: one showing the Export UV Canvas feature, and another to demonstrate the Bounding Box Transformation.

Apologies for not having looked at the most recent SDK documentation before starting this thread. As I am mainly working with R20 I have the R20 SDK documentation installed locally. Didn't think to check the latest online docs regarding macOS development. So sorry! I now see it is quite documented what to do. The yearly cost is a showstopper for me if I want to provide my plugins free of charge. Yet another reason to throw the towel. No need for apologies. It was right of you to point it out, for current and future readers to know the deal. It isn't always Maxon who's to blame 😉

I never implied this was something Maxon related. Sorry if I gave this impression. The topic of this new Apple policy was brought up in the "R25 expectations" topic, and I wanted to discuss this development issue in more detail. Hence created this topic for such discussion what is involved, in order to keep it outside of the original forum thread.

Could we discuss this "Apple-notarization" further? But maybe not in this thread. I have created one specific here: https://www.core4d.com/ipb/forums/topic/115124-releasing-plugins-on-macos-what-you-need-to-know/ Thanks in advance.

I am not an expert with macOS, nor development under Xcode, but for a few years I have been able to create plugins on Cinema4D running on Windows (Visual Studio) and port these to macOS (Xcode). Now, I recently heard about the need to "notarize" plugins on macOS, and was wondering what this is all about. Up to now I used to compile for R16-R21, and could do so on macOS Maverick (R16-R18 ?), Sierra (R18-R20), High-Sierra (R21) Haven't tried S22 or above, and stopped at High-Sierra, since my most recent Mac is a Mac Mini 2012 provided by a generous person. I have an external HD with different partitions, each hosting a particular operating system version. So far - upto High-Sierra - I haven't had the need to have an Apple developer ID, or notarize anything in order for the plugins to work and be used. Then what is the deal with notarizing and all this "protection"-stuff I read about. Can someone elaborate?

+1 on your entire post. Since the release of R21 I seem to have noticed quite a decline in plugin purchases ... that was until I entirely stopped the business due to costs rising way over benefits. My main reason for selling plugins was to be able to get enough income from it to remain up to date with the latest Cinema4D versions. That's one idea down the drain. Now that I had decided to stay with R20, I was looking for the plugins to pay for an Octane and/or Redshift license. Community seems to have decided that's not going to happen. I am stuck on R20 (which I like), but am also finally wondering if I need to get some feet wet into Blender. Over the past few months I have been tinkering to release all my plugins free of charge ... and step away from Cinema4D development entirely. Therefore, I uploaded a free version of EasyUV, hoping to get some feedback to see if it would be worth to make the step to make my other plugins available for free. So far it's been a flop, but it's maybe too early to take conclusions. I have mentioned how I felt about R21 in the past, and seeing what R23 brought us I wasn't too sad I couldn't/wouldn't upgrade. As far as expectations for R25 are involved: I seem to don't care anymore where Cinema4D is heading to. So, maybe it's time for me to move on ... while still enjoying the use of R20.

Thanks for suggesting PETG. I am more inclined in getting the MINI+ as I cannot justify spending the money on an i3 MK3S. But I still have some time before making a final decision, as I first need to tidy up an make room in "the mancave" for the printer, before getting one. ... Not sure that will happen before 2022. The tidy up I mean.

Spend all day watching this 3D printing basics series https://www.youtube.com/watch?v=nb-Bzf4nQdE&list=PLDJMid0lOOYnkcFhz6rfQ6Uj8x7meNJJx which brought me up to date ... and kind of steered me towards the Prusa set of printers. I am looking at the Prusa mini right now, with its 18x18x18 cm, since it's bigger brother I3 MK3S is double the price, for only a tad larger area (25x21x20 cm). And I quite like the USB-stick transfer method over an SD-card. Watching the series I soon realized the resin-thing is not my cup of tea, especially due to the need for specific disposal. I will probably mostly use PLA for 99% of the projects, and some Flex materials for tire-like objects.

Here are some examples to give context to what I described as "small parts for remote controlled airplanes": https://www.thingiverse.com/thing:3584822 https://www.thingiverse.com/thing:3483344 https://www.thingiverse.com/thing:3987006 and then some "not so small" parts: https://www.thingiverse.com/thing:3294927 As an example of "daily used utility objects", some monitor stands: https://www.thingiverse.com/thing:4702580

Over the years I have more than once looked into starting with 3D printing. Mostly to create small parts for remote controlled model airplanes. But also to create utility objects for everyday life. Technology has probably made some huge steps since I last looked at 3D printers, back in 2019. I know I could look up some websites dedicated to 3D printing and read me in on the latest stuff. But I would like to hear from users how they would suggest fellow users to start their journey into 3D printing. What to look for, what to avoid, both in terms of printers and printing material (PLA, ...) What printer sizes to consider: too large being a hassle for storage, too small being limited to smaller parts only, ... etc. Note that I am located in Europe, and due to customs, import taxes, and what not ... I would prefer buying from european distributor. Which means I might not have access to all possible latest and greatest printer and materials available in US or other parts of the world. Thanks in advance