Jump to content

dast

Registered Member
  • Posts

    1,276
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by dast

  1. The Wacom pen has probably something to do with this. The M shortcut (as many other multi-shortcut) opens a sort of popup menu window containing secondary hotkeys. This window disappears as soon as the mouse position moves. It might help to make sure the mouse cursor position stays unchanged, by removing the pen away from the tablet before you press M.
  2. dast

    SPETI and TINA

    Thanks to @bholebholefor spending the time testing out several iterations. We seem to finally have reached a point where all is working as expected. Most issues were related to internal changes in S24, but I managed to fix some bugs I encountered along testing out the latest update. Version 1.22 is uploaded and available in the download section of the forum. For anyone having downloaded and installed a previous version, please make sure to remove any pypv files in your TINA folder before extracting the updated version. And if someone is willing to write some documentation for this, the effort will be appreciated!
  3. dast

    SPETI and TINA

    Something is definitely not right ... I am looking into the code, and notice that the line "TypeError:Required argument 'initw' (pos 1) not found" is probably related to a problem with MAXON's Python SDK documentation. I have informed SDK support, and awaiting their feedback. I am looking at resolving the other issues, but without a S24 at hand to test it's like shooting a moving target blindfolded. One thing you can already try is to : - close Cinema4D, - remove TINA.pypv file - restart Cinema4D That should get rid of all the "'Script Name Extractor ..." issues. Will report back for the other issues ... EDIT: About the "initw", it has been confirmed by MAXON SDK support that this is a change introduced in S24. I have sent you an updated version of the plugin via private message.
  4. dast

    SPETI and TINA

    Thanks for the console dump. It was definitely a Python 3 issue. I have modified the plugin, and uploaded the updated 1.2 version to the download section : https://www.core4d.com/ipb/files/file/43-tina-texture-importer-n-assigner/ Should work with R17 up to R23. And hopefully runs on S24, which I have no access to for testing. The folder should indeed have full write access, since the plugin will create a preference file to remember the last used path. As well as the need for writing presets and image mappings, which you can set up in the Config tab of the plugin
  5. dast

    SPETI and TINA

    In those cases it is always a good idea to look in the console window (shortcut shift-F10) to see if the plugin reported an error. As this is a Python plugin, the best place would be to look into the Python console of Cinema4D. I suppose the error listed there will probably be related to the switch to Python 3.7 in R23 and above. Providing the error message might help me update/convert the plugin to support the newer releases ... thanks in advance.
  6. dast

    SPETI and TINA

    What does make you feel this is discontinued? Isn't the download still available? Granted I haven't updated it to work with the new nodes material, nor does it work with external renderers. And maybe it gives all sort of errors with latest Cinema4D builds? As I mentioned in an earlier post, feel free to provide feedback if it does or doesn't work on S22 and later. One suggestion: don't !!! It was a nightmare to implement.
  7. 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!
  8. I'd like to second this. Having the date/time of the most recent reply to a thread helped me to know if a new reply had been posted. Using your recently posted screenshot, shows at right the number of replies, views and last poster. Similar request as I did with a previous big update, quite some time ago. Here's a "refurbished" attachment from then ... The "old good way" with date/time on top, the newer one without at bottom.
  9. I figured it had to be something like that. Good to know. So, next time I am writing some incomprehensible and useless post, I am counting on you to jump into my account and turn my message into some intelligible piece of information. 🤣
  10. Wow ... what happened there !? Quoting and replying me in my own post. Freaky! But yes, I now see the entry in my account. Thanks Igor.
  11. Sorry to spoil the fun, but "Sticky Notes" is the last item in the menu of my account settings. No "Tip Me Settings" present. Try now! 🙂
  12. @IgorI have a few more issues, but definitely NOT urgent. Just want to let you know about them. I have seen your sticky notes about the Tip Me, but cannot seem to find that menu item in my account settings. I can also not reply to your sticky, as system says I am not allowed to send sticky notes. And my profile says it's 0% complete, while I have almost filled in every possible field, except website. Weird stuff. As I said: don't spend time on these minor issues, I am only mentioning these to let you know.
  13. Small update for this script, as I kept hitting a wall when using this. In previous versions the behaviour was such that the currently selected selection tags were left as is, and the newly created selection tag was not selected. This in order to mimick the original "set selection" behaviour. However, in recent times I found that behaviour working against me. So, I have now updated the script to deselect all previous selection tags and select the newly created one. But I have made sure a user can simply revert to the old behaviour by opening the script in the editor, and replacing a single piece of text. For the new behaviour, leave line 10 as is: gSelectNewTag = True For the old behaviour, simply replace "True" by "False": gSelectNewTag = False New version 1.1 uploaded !
  14. Still wondering about a null control over a userdata. Example: I have a single-mesh snail like character and use a bend deformer to manipulate the neck and head. The bend deformer has a strength attribute, which allows to perform a tilt of the head up-down (nodding yes), and an angle attribute which allows me to tilt the head sideways. Now, I could create null controls to steer de strength, and another one for the angle. Or I could simply create 2 userdata sliders and add them to the HUD. When to prefer using the one over the other solution? Is this purely user preference? Or is there a philosophy behind when to use what?
  15. Hi Igor, Thanks again for spending all this time make for a community available to us fellow Cinema4D enthusiasts. Up to recently I had a silver monthly contribution, which was automatically renewed by PayPal every month. With the change of C4DCafe to Core4D I was assuming the legal part of the payments needed to be changed as well, as such I figured it might be useful that I ended the automatic payments to C4DCafe, and instead continue with payments to the Core4D entity. Taking advantage of this change to go with a gold annual contribution instead. However, after my contribution ended about a week ago, I went to the contribution page and could only find a way to "renew" the silver|monthly. All other tiers, even the annual ones, are inaccessible (see screenshot). When I go to the "manage purchases" page, all I can do is renew the silver|month. Nowhere on the whole website can I find a way to purchase a gold annual contribution. Nor in the "Store", nor in "Contributions", nor in "manage purchases". It seems the system sees I previously had a silver|month contribution ... and doesn't allow me to be anything else 😉 And please, just round up those prices. It's quite silly to mention 4.99 euro per month, when you're actually billed 5 euros. I don't mind being billed an extra cent, and I honestly prefer round numbers. *I* never got with the idea behind this "charm pricing" (https://en.wikipedia.org/wiki/Psychological_pricing) Sorry to bring this up in the forum, and not via private message ... ever since my contribution ended last week I am unable to send PM's, due to a full mailbox 🤣
  16. I could have quoted your entire post, as I agree 100% with all you mentioned. Couldn't have said it better. I stayed out of the discussion until now, as I feel you now have voiced exactly what is on my mind, and wanted to support your message. While I regret not having some of the new features, I am more than happy of using R20 without its periodical need to connect and validate its license.
  17. For as far as I can remember I have been using existing or custom-created textures for my materials (Physical and Standard Render). I'd like to try my hand at some procedural materials now, but have no clue where to start. I know you can use gradient shader as a start to make lines, or use the tiles shader as a base and start building on that. But, for instance, some leopard print, or other spotted animal fur or skin ... how to get started on that? I am looking for basic or advanced tutorials with examples how to construct materials from standard C4D shaders. I know there are similar tutorials for Substance Designer, but the functionality and available shaders are quite different. Any suggestion welcome. Thanks in advance.
  18. Completely forgot about the Python Tag, and what it is capable of. Thanks a lot for sharing.
  19. In the past I have done some simple character animations where I used nulls or userdata to control the rigged character. I never took the time to find out how to use nulls AND userdata ... until today. (Or maybe I already looked for this in the past, and didn't find a satisfactory answer) Say you have a mesh with all the bits and pieces to make up a character, and want it to move or rotate. You could: 1. create a null, and PSR constrain the mesh to the position/rotation of the null. 2. create some userdata/xpresso to handle the position/rotation. You can then add the userdata to the viewport HUD. In both cases you can manipulate the character from the viewport. However, you cannot create both solutions at once. Once something is driven by userdata/xpresso you cannot manually adjust it, except via the userdata control. Or is there a solution for this? Can you have a null and userdata that drive something, which you can keep in sync, whichever of the two you use? And if not, what makes you decide when to create a null control or a userdata?
  20. This isn't a script but a plugin. So make sure to have the folder inside the Cinema4D's Plugin folder. No need to hit Run Script, as the plugin is loaded when Cinema4D starts. If all is well, the plugin should have added a "Search" menu item into your Material Manager. You can use that menu item to launch the plugin's search dialog window. Or you can do the same from the Plugins menu.
  21. As a former plugin developer the idea of going to a subscription model for my plugins had crossed my mind. Granted, that idea didn't survive for longer than a blink of an eye, but it still did cross my mind. Selling plugins is one thing. If you continuously extend the plugins' features and provide your customers with free updates, as I did, you need to rely on some income to justify the costs. However, if you're making your customer pay for the updates, then these ain't "free updates". So, I kept to my principles, remained naive and kept most updates free, counting on new customers to finance the cost of improving the plugins. Until no new customers were left, or at least not enough to justify the cost of running a business. Now, I am not defending, nor justifying those who went subscription. Just saying that there usual is another side to the story. That said, I am pro perpetual and against subscription. I am also wondering what this patreon-thing is all about? To me that's just another subscription model. Or am I missing something? On the other hand ... I don't quite see what this subscription-talk has anything to do with the original topic regarding an Indie version?
  22. Very useful tip there. Never even noticed the render settings had a render region option. Thanks for sharing.
  23. Igor is right that you put a a Python or C++ plugin into the Plugins folder, which you can locate by going to Edit > Preferences, and press the button at bottom to open the preference location. Except that this "Points to Circle" is a Python script, not a plugin. And scripts belong in Library > Scripts. With the Library folder being located next to the Plugins folder in your C4D preference folder. You can put all scripts (and their icons) into the main Scripts folder, or you can arrange your scripts into subfolders. Restart Cinema4D after copying your scripts to the appropriate location. Additionally, you could assign a shortcut to this script, to make it available at a key press.
  24. Are you using the Nvidia game drivers or studio drivers? Do you have multiple views open, or are only using a single perspective view when rendering fails? If single view, have you tried with different views? Again, if it only happens with a single view, have you tried opening a duplicate of that view. Is it rendering black for every view? Does it also happen with the front, side, top views? Or only with perspective/camera view? I guess you have the options to: 1. finish your current projects, and afterwards look into resolving the issue 2. make a system backup now, upgrade to the latest R21 update (since you're on 21.115), and if it doesn't help (or your system "breaks") to restore the backup Have you contacted MAXON support about this? If not, I suggest you do.
×
×
  • Create New...

Copyright Core 4D © 2024 Powered by Invision Community