Jump to content

Juanxer

Members
  • Posts

    142
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Juanxer

  1. I managed to make it work. The issues were:

    • I had Windows 11's Core isolation's Memory Integrity feature on, and it was keeping the Sentinel driver from loading (it shows so in the Device Manager control panel). I had to switch it off to be able to work. I first had to uninstall that more recent version I had downloaded from the vendor (It probably is compatible with that security feature, but EIAS didn't seem to be able to use it) and then just reinstall EIAS.
    • I hadn't installed all four Library packages from your link (I was too accustomed to only use x64 versions, forgetting that EIAS has both 32 and 64 bit components).

    Thank you so much for your help  :)

    • Like 1
  2. Having just migrated from Mac to a brand new Intel i7 13700K-based Windows 11 system, I find that I can't get EIAS 9.1 (and EIModeler, which I was nostalgic about) to run, while I've had not problem managing that on older Windows 10 systems (even on VirtualBox!). The problem is that I'm getting a Hardware Key Error: DRIVER_NOT_INSTALLED error message.

    Things I've done and their results:

    Given all that, I wonder if you have a recipe or sequence for a successful install. Other than Windows 11, the processor might be a factor, as 13th generation i7 come with 24 cores and that seems to be problematic for some old apps somehow.

  3. Nice article about the evolution of ILM's animatics process and its role in The Phantom Menace (by the way, the website it appears on, beforesandafters.com, is a real treasure trove of VFX articles including old stuff like "Speed" or "The Mummy").

    ‘IT COST ABOUT $65 TO HAVE A COLD PIZZA DELIVERED IN THE MIDDLE OF THE NIGHT TO SKYWALKER RANCH’

    (I hope this is the appropriate subforum to post it in :)

    • Like 3
  4. Hola, Tom  :) 

    This morning I've checked a bootable backup from some days ago in which EIAS still worked and have restored it fairly quickly, so for the time being there's no longer any urgency. That said, it probably would be best to post somewhere how we ought to deal with those last updates from Apple.

    In any case, thank you so much for your prompt offer to assist me. You are a lifesaver!

  5. Tomas, might it be that the private messaging isn't working? I sent a couple of messages already.

    As it is 2:00am here, I'm going to go to sleep :) . As I told you, this is not really urgent, and I wouldn't want to ruin your weekend, so we can leave it for monday or later. And, anyway, if there's any permissions settings recipe you might care to point me to, possibly I could take care of it.

  6. Hi, Tomas. As far as I've checked, I'm still on macOS Sierra 10.12.6 (I've been there for several months), and the last significant change done was Security Update 2018-005, which I ran last Thursday, so whatever happened between saturday morning and the following afternoon hasn't been an OS change.

    I'm grateful for your offer for immediate help, but it's not that terribly urgent (I can run EIAS in a PC of mine instead, in the meantime) and I would rather read about those permission problems you mention, if you can point me to some article about them.

  7. I've been working with EIAS on my Mac today normally, and suddenly Animator is failing to launch, showing this message:

    Assertion failed on line 24 of file Dbg_InitCounter.cpp: Failed to call Dbg_InitCounter::ShouldCleanUp() enough times to balance Dbg_InitCounter::ShouldInit()

    then it crashes and produces a standard macOS app crash error dialog.

    As I had shoved the USB key a little while repositioning a side screen, I tried putting it in another USB socket, to no avail (unplugging it produces the usual alert in such cases, so it doesn't seem to be that). Then I tried installing a fresh copy. Upon entering my activation code, Animator shows one of its own alert messages saying:

    Cannot allocate needed 3D icon "IconBody_Camera" from EIResource folder

    Those folder and file are there, fresh from the disk image file. This message doesn't appear when I launch the non-fresh Animator (or possibly it goes out too fast to be seen).

    I've restarted the Mac, without results. Before I try more drastic steps, is this something that sounds familiar to anyone and suggests how to solve it?

    I'm on an old hexacore Mac Pro, running macOS Sierra 10.12.6

  8. For a human head model, I have a Normal Map for its facial features (facial muscles, wrinkles, etc.) and another for a clawed skin scar. Each map works well by itself, but If I stack both of them, the one on top prevails, the one below showing no effect whatsoever.

    Is there any way, any blend mode or any other method, that will mix them as if both features were in a single map? I've been playing with the blend mode of the Normal Map on top, to no avail: No matter which blend mode I choose, the result is exactly the same. 

  9. To my surprise, I found out that mac OS' Quicklook feature (the one that lets the Finder preview a file's content by tapping the spacebar when it is highlighted) works for a few 3D formats such as .obj. Finder's Column view's previews work, too. You can use a few mouse and keyboard combos to move and rotate the camera. Windows 10 has some 3D preview abilities too.

    Is there anything like that for .FAC files, any Quick Look generator plugin for FACTs?

    • Like 1
  10. I wouldn't count on the GPUs or the CPU being officially upgradeable, given that they are mated to the central heatsink via thermal paste. That makes them as upgradeable as the old tower's processors (doable but messy, so unsupported).

  11. Take into account that, Mac-wise, Hexagon is a PowerPC app that requires Rosetta, so it won't run on OS X Lion or Mountain Lion.

     

    Its main bugs: it can crash when opening the app by double-clicking a file, so you better open the app first, then double-click that file. Also, any field-filling by keyboard will turn the main window's objects unselectable, so it's better to do any object renaming or such knowing that it will mean closing and reopening the app to keep on working (the secondary floating window will still work, though).

     

    Until EIAS 8 I had far better luck exporting Hexagon objects as .3DS. Got to try .obj with EIAS 9 now.

     

    It is a shame that Hexagon has been mostly abandoned: I love its featureset, and I use it quite often. It seems its programming was based on some now legacy framework. There was an attempt at turning it into an Universal Binary version, but…

  12. Now that EIAS 9 has been released, we can resume bombarding you guys with our hellish suggestions of features, har har! :D

    Now, seriously: I'm wondering here if the way you've architected this new EIAS 9 will allow for easier and quicker implementing of new "light" features. Say:

    -"Advanced" copy/paste: you select a group or a light or something else and do a CMD-C (or CTRL-C in Windows). Then you do a CMD-OPT-P (or CTRL-ALT-P) instead of the regular CMD-P, getting a multiple checkbox dialog that lets you choose to paste position/rotation/scale data, plus other specific item type-related parameters to a single or multiple item selection in one go. Sort of like Ms Excel's Special Paste, or Final Cut Pro's.

    As it is right now, matching one group's pos/rot/scale data implies about 9 conventional copy/paste operations, or switching to spreadsheet view, drilling down the channels to expose the relevant cells and copy/pasting these.

    -Align/space selected items, Photoshop layers-style.

    For some pretty well-defined things like these, if you would decide to do them, what do you think your "minor" upgrade cycle would be, time-wise? Are things getting easier?

×
×
  • Create New...