Jump to content

Cairyn

Regular Member
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

8 Noble Beginner

About Cairyn

Profile Information

  • First Name
    Ronald
  • Last Name
    Klemp
  • C4D Version
    19.024 Studio

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Let's compare with 2017: My MSA was about 550€, including 19% VAT 595,- if I recall it correctly. This included one year of Cineversity and all updates during that year, implicitly covering the next C4D version. Currently, the price I hear around here for a regular MSA-less upgrade is $999 or so (the old price page is gone so I do not know what the local € price used to be). Since that is a US price it's without VAT. As of today's exchange rate, this is 905,01€ w/o VAT or 1076,96€ including 19% VAT. Now Cineversity used to cost a hundred bucks per year when it was still possible to buy access (not to mention a 300$ fee for the first year just to enter the esteemed halls of learning). As Cineversity is no longer part of my yearly package, I need to add this cost as a hypothetical sum: 100$ = 90,60€ + VAT --> 107,81€. The total sum I would need to spend to get the same stuff I used to get through the MSA is therefore 1076,96+107,81 = 1184,77. Twice the MSA would have been 1190€. That is close enough for me to justify "double the cost". Now, MAXON raised the price for an MSA in 2018 (by roughly 10%!) so if you compare the hypothetical upgrade cost with the 2018 MSA cost, it looks a bit worse for the MSA. And if the Euro price for the standard upgrade was indeed lower, this too works against the "double" cost phrase. But no matter the exact numbers, it is still a significant difference. But lo! don't despair fellow wayfarers, because surely MAXON will see the light and announce a fair price for the perpetual upgrades - which will certainly be the cost of the corresponding timeframe's subscription, won't it? - and also add a voucher for one year of Cineversity. Then, only the grumpiest users will keep complaining (because of the price increase of 20% on top of the 10% from last year, but who's counting?), and celebrations will happen all over the lands.
  2. I'm actually not so sure about the vector thing. Vectors are great if you want to size things up. If you need to restrict yourself to a few pixels, as icons on normal monitors tend to be, and at the same time have fine recurring structures to display, like linework or letters, vectors alone can leave you with lines that are antialiased to invisibility, ugly pixel-aligning artifacts, and rounding issues in the placement of similar structures. Fonts, for example, require a number of "hints" in addition to their vectors to ensure that the stems of letters are the same width, that line weights don't jump around, and so on. The effort needed to create icons that way is considerable. BTW, you should not just take the icon file and replace it with an older version - there will be all the new icons missing, and there is no guarantee that the icons are all in the same place. I have in the past changed the contrast of the whole sheet, and the colorization of some icons I found unpalatable, but I found taking old icon files being pretty problematic.
  3. There was indeed a version in the past (I think it was R15) where the external prefs files were changed so much that it was necessary to start over. Since then I had no issues. It is true that it is a good practice to reassess one's workflow every now and then, though. My personal keyboard shortcuts are systematically ordered - the built-in ones have (partially) nothing to do with the names of the functions they represent. Due to the limited numbers of physical keys, I get a lot of multi-key-shortcuts, like S~P for Select Path or M~K~E for edge cut (modeling-knife-edge). The more functions I wish to put on keys, the less logical it gets (Q as first key for... quick?) so I am thinking about replacing a number of these by custom popup menus or simply by the "circular" menu. But I can see myself overdoing it again...
  4. Well-l-l... The way C4D organizes its interface is a bit complicated. You may want to start with the installation directory and look how it's set up. 1. Under resource\modules\c4dplugin\icons you will find a .tif that contains the majority of the function icons. This file is interface_icons_2x.tif. There is also a text file interface_icons.txt that contains the function IDs the icons are assigned to; partially with cutouts. 2. Under resource\modules\c4dplugin\schemes there are directories for every scheme that C4D provides. Namely, Light and Dark. Within these, you find the .col file (with the basic colors for interface and viewport), the .res file (which tells C4D at what coordinates to find certain graphic elements), and finally the images with the graphic elements themselves, normal.tif, focus.tif and disabled.tif. These provide button snippets, borders, arrows, checkboxes, scrollbars and other things that are not icons and/or can be resized. 3. Note that the R21 has these three files also in a double resolution version marked as "x2". I suppose these are for the hi-res monitors. 4. Also note that the R21 has a new format for the files with two layers, whereas the R19 was working with transparencies. I could get the R19 files to work but no guarantee for the future (also, I didn't yet test it in depth). 5. Now, if you want to build your own scheme, that will go into the Home directory, not the installation directory: Cinema4D V21_xxxxxxxx\library\schemes 6. Copy the scheme you want to start with from the installation directory (either Light or Dark) by copying the full directory thus named, and put it into the schemes subdirectory of the Home directory. Rename the directory, the .res and the .col file appropriately - the new scheme will appear under that name in the Preferences dialog. Now you have a clean setup for a new scheme. Always work in this copy, and never change the files in the installation directory. 7. If you need to modify the icons (for example if you want to modify the background color - several icons appear directly on the background and must have sufficient contrast) you can copy the interface_icons_2x.tif and the interface_icons.txt directly into your scheme directory (e.g. Dark2). The original Light scheme does this for example. 8. If you are reusing a scheme from a previous C4D version: There is NO GUARANTEE that the graphic element files are still usable. There may be new elements needed, or old elements deprecated. 9. If you modify the colors: Some colors are just references to other colors. Some colors depend on each other (e.g. text color and textfield background color). There is no tool that shows the dependencies in an easy way, or would show all GUI elements that are using a certain color, icon, or graphic snippets. It's easy to get lost in the plethora of settings. 10. You can theoretically edit the .col file with a text editor. This will help you seeing what colors you changed and what colors were in the other version's .col file. However: Always start out with a .col file from the current version's scheme to make sure all needed colors are defined. Other than with the shortcuttable.res file, missing an entry will cause errors. 11. If you decide to NOT edit the .col file manually, but use the Preferences dialog, upon exiting the program a new .col file under the scheme's name will be created in the prefs folder in your Home directory. This has the advantage that you keep the original color settings in the schemes directory. Comparing these two files is also the only way to find what colors you have changed, because C4D will not just store the changed colors in prefs, but the full set. If you want, you can use the prefs version to overwrite the schemes version but I'm not sure whether this is advisable. 12. Should you ever get into a situation where C4D crashes on start because of that, shows error on start, or gives you a totally unreadable interface, first try deleting the .col file from the prefs folder; if that doesn't help delete the current scheme folder from the schemes directory. Now have fun ruining your GUI
  5. hmm, what's your issue with copying the shortcuttable? I just did that for R21 (as I did it for many years and many versions) and it seems fine to me. Of course, new shortcuts for functions that have just been introduced for the R21 will not be there. Like for example IDM_UVEDIT_UVGIZMO TARGET_59500 CTRLCMD+"T"; But adding these (or adding more suitable shortcuts in one's personal pattern) seems much easier to me than recreate the hundreds of shortcuts I already assigned. (Also, if you have assigned shortcuts to scripts you may need to recreate those. I am not sure how C4D assigns the internal script IDs (as a script does not come with a constant plugin ID), I once ran into an issue with these.) Remarks: 1. The shortcuttable is a readable file, you could put it into an editor and do a compare. Unfortunately a lot of commands are named like PLUGIN_CMD_4650004764 instead of being human-recognizeable. 2. The original shortcuttable now seems to reside in the installation directory under resource\modules\c4dplugin\c4d_shortcuts.res (Windows). This is a new name for the file, and there seem to be some changes in content as well (CTRLCMD?) but the R19 shortcuttable.res copied into the prefs directory in the Home so far serves well. 3. It might be possible to write a plugin to manage shortcuts from these files. But as it is just a one-time effort per release, I don't see that anybody would pay for that, and as a programming exercise it's just too much effort.
  6. Well... search for a file named interface_icons_2x.tif in your installation directory and see for yourself. No vector based icons here.
  7. That is at least how it feels at the moment (which makes me sad). Although the upgrade prices to R22 are not known yet, the majority of users is assuming that it will be similar to previous non-MSA upgrades, which would (if you financially take the now-missing Cineversity into account) mean a doubling of the 2017 prices (2018 already saw a price hike, and now this...). The best way for MAXON to say "We are still committed to Perpetuals" would be to announce that the upgrading of a Perpetual will be equal to the cost of the corresponding timeframe's subscription. As easy as that. It would certainly not solve the issues of oldtime Prime/Visualize/Broadcast users, and it would still phone home, and it is still more expensive than last year's MSA, but it would feel a lot more fair than the current pricing expectations. Yes, fairness is the word here. Perpetual users are already saddled with an upfront cost (which they have paid already and cannot fully retrieve), and they suffer from getting updates later than subscribers. There is no reason to punish them with much higher yearly cost on top of that - except to intentionally make that choice unattractive. Since the "R22" would be virtually identical with what subscribers receive at the same time, there would be no "separate version issue" either*. If a customer feels treated unfairly, there will be resentment. Resentment leads to angry threads (lots of them, not just on this forum but on those of other software too), and to customers leaving the fold. That cannot be part of the strategy, no?** * Only exception to that would be if MAXON wants to release a pure bugfix version for Perpetual users, which necessitates keeping the bugfix branch separate from the feature branches. But as we don't have seen any new inbetween versions yet, this might very well be the 21.1 anyway. Plus, retaining customers may be worth the additional cost. ** "The only bad publicity is no publicity"?
  8. (Writing this without having read the upcoming posts, sorry in advance for duplicates ) Well, personally I liked the help very much as it was in the past. In a dockable window (so I can keep it in the foreground if needed) and offline so it is fast, reliable (in case I cannot get internet), and independent. The primary usecase for that is: looking up a parameter. What does it do; is it what I think it is; what is it limited to; what was changed in which version. Usually that is solved by a short and concise text and maybe an image or two. I rarely need videos or "community contributions" for that. The help in R20 and before gloriously solved that. To be clear, it's a help system. It is not a forum; it is not a tutorial series; it is not an introduction to 3D. While all of these may be useful if linked, it's not what I need in a help system about 99% of the time. I may want the 1%, but I can live with it being online and occasionally not available and just linked into the WWW. As far as updates are concerned, I wonder how often that would happen. New features would need updates naturally; error corrections would require updates; improved help would be good to be updated. All of these can be published during a release. Everything else is not going to be updated very often, if past experience is an indicator. Or needed to be updated. Again, it's a help system not a forum. It doesn't need to contain live discussion threads. The central information I expect from a help system should be there together with the functionality it refers to. Really, it's not as if I would be against added content in the help. Far from it. But if the price is that the essentials get online'd and therefore are sometimes out of reach when I urgently need them, the price is too high to pay. Oh, speaking of videos. These are not, perhaps, hosted on Cineversity? Because someone cancelled my MSA and I am losing Cineversity access shortly because of that. Which makes any additional video content completely useless for me anyway. And should the help contain any essential videos (so essential that I would like to have them available offline too) that also are moved to Cineversity (Vimeo) as a server, then I am short of content here. Hope that is not the case. Now, it's not that the help is written in HTML directly (a simple look at the sources confirms that). MAXON is using a content management system obviously, and that should easily make it possible to differentiate between internal/local and external/online links. The easiest way of solving the issue is: C4D contains a jump point in its preferences which is a base URL where the help content is located. The user can install the help offline and set the jump point to this local installation; or if they are okay with online only, they can leave it pointing at the MAXON servers for online help. Then, the content management system uses links relative to the jump point for all essential linkage in the help. Everything else, like you said, community content or tutorials or even late add-ons, can be kept as external/online links to be updated live. It's not core material so I bet everybody would be okay with it being online. And you would have the best of both worlds, the core stuff offline and always at hand, and the add-ons online and always current. Oh, and while I'm at it. Cineversity. Yes I see that it takes time and money to upkeep, and all. And everything that is seen as an investment is jealously guarded. But Cineversity probably hasn't made much additional money for MAXON (yes I know, it's MAXON US so there is maybe some conflict in ownership...) as the access has been given away for C4D MSA holders for free for years now, and in the future all the coveted subscription owners will also get it as an add-on. And right now it is causing issues because Perpetual license holders are going to be cut off (because, y'know, someone cancelled all the MSAs). And it's not really living up to its full potential. Here's a revolutionary suggestion (you're not going to like it): Make it public. Yep, public as in no loger protected like the crown jewels. It is an add-on to C4D. It is being taken for granted by many C4D owners by now. Some of the really valuable content (like all those Siggraph talks) is put on YouTube anyway for free. And it's not that useful for third parties - who'd want to steal it, except maybe software pirates who can do it anyway no matter how many locks and trapfalls you put on it. Or holders of a perpetual license who are no longer updating... but hey, a little generosity towards them would go a long way too. With current tech, undesired deep links from other people's sites should not be a big issue either. A lot of issues would just disappear. A user could download a tutorial and watch it at the beach (where they don't have internet connection) without jumping through hoops first. Perpetual holders would be happy again (at least as far as that point is concerned). You can link the tuts from the online help with no further thought on access regulation (and, I guess, many less browser errors). And who knows, maybe someone who's currently using some different software would watch a C4D tutorial and decide, "wow I really like the way Cinema is doing things, I guess I try a subscription for a month or two and have a looky whether this is a program for me". Acquiring new customers, and such. Yeah, you're not going to do that, I know. But one can dream.
  9. Considering that the R21 is only out for ONE DAY, I wonder anyway where he got that idea. People haven't had time yet to complain. Whom did he ask? Betatesters who probably sit in an office with perfect internet connection and haven't needed the help while on a plane?
  10. And what happens if e.g. I stay with R21 Perpetual, and MAXON decides to no longer support older versions? Let's say they are at R25 and don't want to support more than 3 old versions, AS THEY ALREADY HINTED AT? Then, my R21 is not only no longer downloadable, but my existing installations also don't have a help system anymore b/c MAXON kills the online help? And while I may st Not to mention situations where you simply DON'T have online access? It's nice if you live in NYC or LA and never get any issue with your online access, but some people would like to be elsewhere or even traveling where the internet access is not stable or nonexistent. Yay, working on a transatlantic flight for 12 hours, no internet here, no help... awww. Putting something as essential as the help (which you may need any second of your workday) online only where you may or may not be able to see it is a BAD BAD BAD idea. What's next, back to stupid terminals and putting everything in a cloud? Oh yes, I see. Also, what about "a few isolated requests"? Up to R20, the help WAS offline, so where should any requests come from to MAKE it offline? It was the default, of course you're not getting requests for the default. If you're lacking requests, here, have mine: MAKE THE HELP ACCESSIBLE OFFLINE AGAIN. (And "Agile"? Really? If your development method necessitates the delivery path, you're doing it wrong.)
  11. Is that a joke? So if I don't have online access, I don't get to see any help files?
  12. (Just don't call it "hotkey" if it's actually a standard keyboard shortcut. Hotkeys in C4D lingo are special keyboard shortcuts where you keep the key pressed while you do something with the mouse; e.g. Rotate Modeling Axis, Disable Axis Handles, or Weight Subdivision Surface. The functions that can be activated by hotkey are predefined and listed as such in the Customize Command window. Just to keep the terminology right...)
  13. You can change all the keyboard shortcuts as you like, even use multi-key shortcuts; or you can define your own toolbar; or you can script something to open a popup menu with all the options and bind that to a single key... C4D is just that configurable.
  14. I vaguely remember that you need a Quadro if you want to use a stereoscopic monitor because of some buffer reasons. No idea whether the RTX cards meanwhile support the same. For standard applications I wouldn't bother with a Quadro. On the other hand, two RTX cards make only sense if you are rendering on the GPU, and not all renderers have specific RTX support yet, so it may be a bit of a future investment.
  15. Watch out for which axes really get rotated if you are using the viewport rotation gadget. The gadget is oriented to the child's coordinates while the actual rotation happens in the parent system. Look at the attribute managers rotation values to verify, or have a look at the f-curves where you should see two constant lines for the unused angles. You may think you rotated only one axis (by gadget) when in truth you rotated two. -- Another issue may be if you rotate by more than 180° which can cause funny interpolations; hard to say without a scene. If you need to rotate around several axes, you may want to switch on Quaternion Rotation which uses the shortest path between two points on a (hypothetical) sphere describing the motion. However, the Quaternions come with their own set of issues.
×
×
  • Create New...