Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Be.eM last won the day on November 25 2021

Be.eM had the most liked content!

Community Reputation

3 Neutral

About Be.eM

  • Rank
    Advanced Member
  1. Thanks, Tomas, it was worth asking, though :-) Bernd
  2. Hi Tomas, I know this is going to be a necro-bump, but… I've just opened and rendered a project in EIAS v9.1, using one of the old Konkeptoine C3 shaders (simple water). I got an error message from Camera, while using the 64 bit version. Switching the camera to 32 bit solved the issue for now, and the shader rendered. I suppose a 64-bit version of these old shaders is not (or no longer) available? Thanks, Bernd
  3. Well, that's how it is advertised. However, it's primarily a good thing for the shareholders of the company in question. I haven't seen many new features in Adobe software that really make a difference or would have been a reason to *buy* an upgrade. Something is developed, some new features appear and get some hype, but still working functions get broken during updates, while other - long requested - features are not implemented. I don't mind an *option* to subscribe. But I really hate it if it's the only option.
  4. Please keep the dongle (allows me to switch between as many machines as needed), and please don't start that evil subscription thing. At least not as the only option. Just think about it: if you had bought EIAS 9 via subscription, how much would you have paid for the same piece of software until today? I'm still working with several Adobe Creative Suites CS4/5/6 which have been fully paid for years, and which perfectly do everything I need. Why pay again and again for something that still does the same things (for me) as years ago? And even worse: for something that stops working if I stop pay
  5. We could try the PolyTrans route. PolyTrans natively reads/writes EIAS FACT and C4D formats, so it's worth a test. I have no experience with such conversions (poly -> poly including textures), but I'd probably need the FACT model plus the corresponding texure folder. If you want to test this, just send a mail… doesn't have to travel far, it only goes to Bavaria, Germany ;) Bernd
  6. Christmas cards, annually rendered in EIAS since 1997… :)
  7. Cool. You must be the first member from Vulcan here :D Bernd (also speaking a different language)
  8. Ahhhhh… sometimes talking about problems solves the problems instantly. I shouldn't have activated the "premultiply alpha" option when opening the image in Photoshop. Sorry :blush: Bernd
  9. Tom, I'm not sure if this is a bug or just a misunderstanding, so I'll post it here. Main issue: Rendering against background colors set in the camera/background options doesn't make it this way to the saved image file. Expected result: color of the transparent red strip should be uniform across the whole length, as it's seen above white plastic and the white background. Actual result: non-uniform color output, the white background setting is ignored when saving the file. If I remember correctly, I already HAVE used this function (rendering transparent objects over white camera
  10. Well, I can sell you my old EIAS ADB dongles. They create those warmer looking vintage renderings. Much better than that modern USB crap :D Seriously: doesn't modeler, like the EIAS application itself, save it's serial number and unlocking code on the disk after installing and initializing it? You can't use EIAS with two dongles (except you're installing two copies and only use it with the corresponding dongle), and I could imagine it's the same with the modeler. Bernd
  11. Because Maxon keeps (or kept) the specifications secret. I guess PolyTrans being the "Engineering" part of the "C4D Engineering bundle" helped Okino to learn about the format.
  12. Scott, while all the formats Tom mentioned will probably work, there's another way which seems pretty unknown to most of the C4D (and EIAS) user community: As of 2012 or 2013 (not sure about the exact release date) Okino PolyTrans is able to read and write native C4D files (the only application apart from C4D itself), as well as FACT files (which it always did). Maybe worth a test, as it provides the use of native model files in both directions. I'm sure there are some parameters or conversion settings to be tested, but I was very excited to hear these news from Robert (Okino). Ber
  13. Steven, joining objects in FZ is a good way to simplify material handling. I often do this with e.g. hundreds of screws that don't need to be handled separately. Generally a master material with a diffuse map makes sense, if the diffuse map is a shader. Not so much with an actual bitmap image. However, you could still use a master material with a bitmap texture as "Copy-Paste source". Copy the master material parameter set, and and simply paste it into the material windows of the objects in question. There you can individually adjust size and positioning of the map, without having to enabl
  14. I've seen such streaks with imported CAD geometry, when single points are displaced (due to a failure on export or import). Happens sometimes on rounded edges or the seams between NURBS surfaces, and sometimes translates into facetted geometry, too. Bernd
  15. Brian, I've tried to catch it all in one picture... For this example, I did the faceting already within FormZ, but the same thing happens when exporting smooth geometry from FormZ using the corresponding options. I believe the key is the option "Additional Faceting", which is something EI Modeler does as well. The attached picture shows simple rounded cubes, the first left smooth, the other ones converted to facetted. From those facetted ones, the leftmost one is without additional faceting, all the others with this option and different parameters. I have NOT adjusted any resolution pa
  • Create New...