Jump to content

Welcome to INSYDIUM ONLINE

The place to talk about X-Particles and Cycles 4D

Steve Pedler

Administrators
  • Content Count

    19
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Steve Pedler

  1. Steve Pedler

    Hardware requirements

    I'm sorry, I can't give you anything more I'm afraid. It's not possible to make hardware recommendations, there are simply too many variables - CPU speed, number of cores, amount and speed of RAM, and so on. And the hardware affects different parts of XP differently - whether more cores or higher CPU speeds are better will vary depending on what you are doing. We have a very wide variety of systems that we've tested and the only conclusion we can come to is that it's not possible for us to advise on hardware. That's why I emphasised this was a purely personal opinion and definitely not an Insydium recommendation.
  2. Steve Pedler

    ThinkinG Particles tab

    Thinking Particles are not included in all versions of Cinema, so at a guess you are using something other than the Studio version. If so, there's nothing you can do (except upgrade to Studio). Steve
  3. Steve Pedler

    Hardware requirements

    Basically, you need a fast processor with plenty of cores 🙂 But seriously, my personal opinion (not talking for Insydium here) is to stay away from Threadrippers - they have large numbers of cores but the slower clock speeds give disappointing results in simulations. The i9 you've suggested is a good bet. If I was building a new PC I'd go for an i9 of some kind. Xeons do quite well but we have had people with Macs and dual Xeons reporting slow speeds, so again, it's an i9 for best results IMO. Steve
  4. Steve Pedler

    Graphic cards Display Problem

    What's the problem? That's as it should be. Steve
  5. In the Trail object, Thickness & Color quicktab, turn on 'No Thickness or Color Data'. If this switch is off (the default) the spline renderer will use thickness data stored in the trail, overriding the Size settings in the material. But if it is turned on, no thickness data is stored so the material works as expected. And interestingly, that has found a bug we didn't know about. If you turn that switch on, play a few frames, then turn it off, Cinema will crash. So don't do that 🙂 We'll fix this in due course. Steve
  6. Steve Pedler

    xpTrails will not render correctly

    It seems to be due to using the Connect object in the follow surface modifier. If you make that Connect editable, and use the collapsed object in the modifier, it works correctly. TBH I'm not sure if this is a problem with XP or the Connect object, but I suspect that at heart it's due to Maxon's (lousy) priority system. If so, there's not much we can do about it. Steve
  7. Steve Pedler

    Cinema crashes

    Thanks. Try turning off threading in the emitter, that fixes it for me .It's only a workaround of course, but will keep you going until we fix the problem. Steve
  8. Works fine for me. Try another zip utility, I think these were created with 7-zip. Steve
  9. Steve Pedler

    Scale with ease

    Yes, I think I see what you're trying to do. If I understand correctly, you want to have each particle reach its maximum size at the same age. As it is now, the smaller particles reach that final size first, the large ones last. This is because what the modifier is doing is to increase the radius of each particle by the same amount each frame, regardless of how big or small it will eventually be. What you need is for the particle radius to be increased by a percentage of its final target radius each frame, so they all scale up at the same rate. There's no way to do that as it stands because the final target radius is not exposed to the data mapping. I'll have to think about this and see what might be possible, but I can't see a way to do it with the modifier in its current form.
  10. Steve Pedler

    Scale with ease

    No, what I meant was, keep the settings as you originally had them and data map the radius change parameter. Your original settings gave a uniform increase in radius with age, if you map this parameter to age then the increase in radius will be slow at first then get faster as the age increases.
  11. Steve Pedler

    Scale with ease

    Data mapping is the way to go here. Map the 'radius change' parameter to particle age, adjust the age range to whatever you need, and tweak the mapping spline to give the look you want. Steve
  12. Steve Pedler

    errormassage

    Please look in the C4D console, there should be a message there saying 'Cinema 4D Bridge Build xxx....' What is the three-digit build number it shows there? (I can't reproduce the error here.) Steve
  13. Steve Pedler

    Emitter Editing Tab Delete Points

    My guess is that you are using R20. There is a known problem in R20 which means that this operation (delete) does not work. This is not a bug in XP or the Insydium Bridge but is in C4D itself. We aren't sure if this intentional or a bug in R20; we have approached Maxon for help with this but haven't had any comeback yet. In the meantime, unfortunately this is a limitation in R20 at the moment. Steve
  14. Steve Pedler

    Cinema crashes

    This is definitely a bug. Please post a bug report using the bug reporter in XP, so it is entered on our database and won't be forgotten. In the meantime, you can stop this by turning off threading for the emitter (emitter Advanced tab, uncheck 'Threading'). It will make the simulation a lot slower but it won't crash, as far as I can tell. Steve
  15. Steve Pedler

    errormassage

    Yes, the problem may well have been fixed in a later bridge version. Good idea to try that first.
  16. Steve Pedler

    errormassage

    It's entirely up to you whether to use the CD Tools or not. We aren't supporting them in terms of bug fixes in the code but that error is either a resource error (which is easily fixed - Maxon tightened up the resource handling in later C4D versions and errors occasionally crop up) or it's an error in our Bridge plugin. However, I can't duplicate that problem - there's no such error on my system, so it's difficult to comment further. If you want to post a very simple file - just the tag and something to hang it on - I can see if it occurs here too. Steve
  17. Steve Pedler

    Will existing forum uploads be moved?

    We certainly hope to do this, but we are extemely busy at the moment. When the old forum closes we'll look at this again and hopefully find some time to move them across into this new forum. Steve
  18. Welcome to the Shared Uploads sub-forum. This is intended for users to upload things they want to share with other Cycles 4D users, such as materials, node groups, and OSL scripts. Please read the terms of use below. Your use of this sub-forum assumes that you understand and accept these terms. --------------------------------- The Rules 1. What you can upload You may upload the following assets: * Cinema 4D scene files where Cycles 4D is used * Cycles 4D materials (just upload an empty scene with the material in it) * Cycles 4D node groups (these files have the extension .cyg) * Open Shading Language scripts (extension .osl) If your files are large, or the asset contains multiple files, please zip them up and upload the .zip file. 2. What you should not upload Please don't upload: * your renders and animations created with Cycles 4D, these belong in the main forums * Cinema 4D files and assets which don't have anything to do with Cycles - whatever you upload must be relevant 3. What you must NOT upload (and which may get you banned) DO NOT upload: * commercial material or material derived from a commercial source; for example, if you obtain an OSL script from a paid-for book or online tutorial, you cannot upload it here * assets derived from public domain material where the licence does not allow you to upload it to other sites * software of any kind or any other executable file * material which has been pirated or which is obscene, defamatory, illegal or in any other way likely to be harmful to other users or to INSYDIUM LTD, as determined by us 4. Screening All uploads will be screened by a moderator BEFORE being made available to other users. --------------------------------- Other than that, feel free to upload your materials, etc. and discuss how they are built and used. Thanks, The Management
  19. Welcome to the Shared Uploads sub-forum. This is intended for users to upload things they want to share with other X-Particles users, such as XP presets, scene files, etc. Please read the terms of use below. Your use of this forum indicates that you understand and accept these terms. --------------------------------- The Rules 1. What you can upload You may upload the following assets: * Cinema 4D scene files where X-Particles is used * X-Particles presets saved by the preset system in XP * Python scripts for use with X-Particles If your files are large, or the asset contains multiple files, please zip them up and upload the .zip file. 2. What you should not upload Please don't upload: * your renders and animations created with X-Particles, these belong in the main forums * Cinema 4D files and assets which don't have anything to do with X-Particles - whatever you upload must be relevant 3. What you must NOT upload (and which may get you banned) DO NOT upload: * commercial material or material derived from a commercial source; for example, if you obtain an asset from a paid-for book or online tutorial, you cannot upload it here * assets derived from public domain material where the licence does not allow you to upload it to other sites * software of any kind or any other executable file * material which has been pirated or which is obscene, defamatory, illegal or in any other way likely to be harmful to other users or to INSYDIUM LTD, as determined by us 4. Screening All uploads are screened by the moderators BEFORE becoming avaialble to other users. --------------------------------- Other than that, feel free to upload your assets here. Thanks, The Management
×