New changes to EiAS!!!


#23

Arktype is right. v6.6 is mainly about universal binary, however, I think the migration over to Xcode is going to result in a few more enhancements to user interaction with the program. (Mouse scrolling and so forth for Mactel users)

As for a “features” list…I’ll try to get EITG to finalize something for us. But from what I know so far, new features are brewing but they’re intended for v7. But you never know, there might be something for v6.6. (if there are, they will probably be minor) I’ll keep you posted.

v6.5.2 PC & PPC are nearly identical to v6.6 Mactel. Depending upon what EITG plans to include in v6.6 will really determine if PPC and PC owners will want to upgrade. Mactel users are the primary group affected by this upgrade.

The primary issue for v6.6 UB migrators will be the 3rd party transition. Since Blair has immediate access to the SDKs he’ll get the jump on his products right away. Paralumino and Konkeptoine will migrate as well…but there are a lot of products to update there so it will be approached in a step by step manner. Don’t expect everything at once. David Argemi has commented to me that he fully intends to update his specific shaders and wants to keep the migration as free from cost as possible. Paralumino takes the same position. Triple D has commented to Blair that they also intend to migrate. The only 3rd party vendor in question upto now is Onyx. So I’d suggest we start petitioning them ASAP.


#24

And ooops… sorry Jens. Since XP is integrated, I keep forgetting to mention it. Thanks for your update.


#25

I’m a hobbiest at this time and won’t be going to 6.6 [currently at v5.5], but I’m curious if this upgrade means, for those of us folks with older machines [1999 antique g4/400…still works fine], that EIAS and 3rd party companies are now starting to move away from the PPC and older machine/OS/EIAS ver. support.

Cheers, I hope this next phase in EIAS’s history is a successful one for the Users and EIAS.

~Mike


#26

Mike…

I believe EITG and the 3rd Party companies fully realize that there will continue to be a PPC market for a long time. It would be foolish to cut off those users. EITG has managed to keep OS9 users active all the way up through v6.5.2. However, right now they’re supporting 3 Operating Systems. (OS9, OSX, and Windows). By adding Mactel, they may consider finally closing the door on OS9. I’m not certain. But I’ll ask for you.

3rd party developers tend to ride on the edge of development. (Attempting to take advantage of any new technologies integrated into new versions of EIAS). My guess is most will continue with that strategy.


#27

The question was asked to Matt Hoffman regarding future OS support. His answer was:

"With the advent of v6.6 OS 9 will no longer be supported.

We haven’t made any decisions yet about further PPC support. My guess is that we will continue to support it for some time since XCode easily spits out both versions."

So my take on that is, PPC users will be fine for quite some time. Windows will proceed as normal.


#28

Maybe they could do us PC users a bit of a favor and fix the issue where when we close EI it crashes and we have to “end task” on it. I’m not sure if that happens for anyone else regularly but it happens to me quite a bit.

Nothing major but it’d be sweet!


#29

Well, it’s not only on PC it crashes when quiting - the same for me on my Intel iMac. Quit EIAS 6.5.2 and boom - it leaves rather gracelessly.

As you say, nothing major, but still, it ought not to be like that.


#30

Jens,

Since XP was mentioned… will “some” new features make it into XP :slight_smile:

pretty please… I have so many scripts in my head ready for work

Cj


#31

Congratulations to EITG, EIAS and the Council.

My dongle should be on the way, and my MacPro is waiting.

God Bless and Much Sucess.

Alonzo

BTW, I’m glad you are offering an affordable upgrade for MacTels, so at least people can be up and running on MacTels before they go into a longer development cycle. Who know what’s next? Resurrect EIM? :slight_smile:

Dont’ forget me, I want smooth easy ZBrush intergration. No more cutting up Photoshop files :slight_smile:

Oh. and vertex animation import with FBX…

oh what the heck! give me all the character and film productions tools you can muster.

I’m ready for anything!!!


#32

You know what? It is very exciting to hear all the gang of developers commenting policies, timetables and such. If anything, it feels so fresh…

I am curious: do you think transitioning to Xcode will allow for integrating some OS X features here and there that were somewhat difficult to do before? Say, some GUI things like mousewheel support, perhaps Spotlight-based asset autosearch, I don’t know. What do you expect from it? EIAS is based on some multiplatform framework, I believe. Is that a limiting factor for its GUI development?


#33

To a degree, yes.

For instance, mouse-wheel support was simply impossible before because EIAS used the classic (as in, OS9) events manager. However, as has been mentioned by Blair, EITG is now able and is indeed looking to implement it in a future version.

Ian


#34

Hey Ian…

I was under the impression from Blair that mouse wheel support made it into v6.6. I guess I’ll have to check with him.


#35

Interestingly, one of the great features about EIAS v6.5 was that it was OS 9 compatible(!)

I wonder, did EITG even bother inquiring about how many users still use OS 9? I am certain that there are more than a few users out there with G3/G4 desktops with limited RAM that would still be interested in having EIAS… especially if it’s the only remaining 3d animation packages out there available (for OS 9). :slight_smile:

Just a thought before the plug is pulled…


#36

So there ARE new features… the scroll wheel support in the project window would be a very nice addition.

Cj


#37

Speaking of changes…

The Advisory Board would like to begin discussions on EIM and its potential resurrection as a separate application. There’s obviously a need for a full fledged modeling package included with EIAS in order to return EIAS back to a “primary” app status and thus compete with the likes of other packages that include modeling tools.

Discuss the all the possibilities:

  1. Would you want a UB version of EIM?
  2. What kind of upgrade price would you pay for it?
  3. Would you want it offered standalone?
  4. How much would you pay for a standalone version?
  5. Should EI go with EIM or create something entirely new?
  6. Due to the base differences between EIA and EIM and the way the two handle geometry, should EIM evolve into the next EIA? (In other words, should EIM eventually include next gen animation capabilities?)
  7. Should EIM be capable of accessing Camera by itself?

edit: Or would you just be happy with EIM as it was in the last incarnation, with bug fixes, but as UB.

We want to hear from you.


#38

Hey Brian,

Add a new Thread to EIM resurrection…

  1. Would you want a UB version of EIM?
    YESSSSSSSSSSSSSS
  2. What kind of upgrade price would you pay for it?
    $200/$250 = new tools + bug fixes
  3. Would you want it offered standalone?
    Yes, EIM 6.6UB and a upgrade bundle later with EIM 7 + EIAS 7
  4. How much would you pay for a standalone version?
    $500
  5. Should EI go with EIM or create something entirely new?
    EIM, then get the EIM structure and add a new framework based in EIAS with a new GUI.
  6. Due to the base differences between EIA and EIM and the way the two handle geometry, should EIM evolve into the next EIA? (In other words, should EIM eventually include next gen animation capabilities?)
    like I answered in the last question… if EIM could add a way to edit polygons + ACIS… will be perfect.
  7. Should EIM be capable of accessing Camera by itself?
    Right now?, no. If EIM become the next EIAS appl. sure.

Tomas


#39

Yes. I suppose that would be best.

Creating new thread.


#40

Well, since you are honestly considering EIM… I will get together a group of the characters and things that we have created via EIM…

Thank you for the attention to EIM, it is a well loved app!

Cj


#41

Discuss the all the possibilities:

  1. Would you want a UB version of EIM?
    AVT: Yes, if the modeler was on par to current modelers in advance Poly editing, NURBS, and multi-level SDS.

  2. What kind of upgrade price would you pay for it?

AVT: Depends on my jobs, how much I have already invested, what the competitions is charging. And considering I haven’t spent loads time testing, beta, bugs fixes, and rechanneling my Maya modeling knowlege. I would compare it to Maya, Modo, C$D and Silo and offset that by Free modelers like Wings and Blender. Sum all that up then consider how well that regardless of all those factors, it would have to serve as a utility where the others fail as in the case of FormZ. When ever I need to take a Model from Maya to EIM, I need FormZ. When O2F or Transporter can’t manage, then I need from FormZ. So EIM would have to be built so strongly to the core, it will stand when all else falls.

Not to mention, it would be worthless, if it did not have an UV editor and fast hybrid Peltor for UV instantly.

Also, the cage modeling would need higher level poly editing. Like soft modifications, sculpt paint like Artisan, Modo and Zbrush. It must performe fluidly on groups of polgon.
BY THIS I MEAN, brushing geometry, or multiple groups of vertices, NOT subdivision or microploy sculpt painting.

And I would want true SDS’s which have levels of detail, and not just subdivide.

So even if I didn’t have the out of pocket budget right away, if it met my needs, I would find a client to help out.

  1. Would you want it offered standalone?

AVT: Yes, Absolutely. At first. Then it won’t get in the way of Animator, long development.
Perfect it then combine it but at the same time, start pushing Animator’s core closer to EIM where I can be melded with different geometry types.

  1. How much would you pay for a standalone version?

AVT: I don’t have the answer to that right now but “The going rate”. If I had big clients at the time, I wouldn’t care how much it cost. Right now, I’m studying and will only work for select freelance work.

  1. Should EI go with EIM or create something entirely new?

AVT: EIM have a beatiful interface and feel. if you can salvage it, yes. However, I believe there’s so much work, SDS, UV editor, that you would have to redo.
I love the interface and the floating palettes.

  1. Due to the base differences between EIA and EIM and the way the two handle geometry, should EIM evolve into the next EIA? (In other words, should EIM eventually include next gen animation capabilities?)

AVT: I think EITG should be resource conscious. Many just want an update to Modeler. If that’ will get currency into development, give the people what they want (especially if it inspires development and fill the need). No one handles fact file like EIM.

I thnink it’s a complete waste of resourse to add animation capabilities to the modeler, in leu of Animator. I believe Animator should be developed in model animation types like importable NURBS, animateable vertice animation, CA tools, ZBrush, (and FBIK Auto Rigs. and dynamics, cloth, hair, wmps, IK spine,) to make it full flege film systems. More importantly MEL like, XP core to address flexiblity and diverse demands of film. XP should be the glue between all the plug-in. One interface to override all interfaces in the whole environment.

  1. Should EIM be capable of accessing Camera by itself?

AVT: Of course. Every app should be able to access Camera. EIM should not be reduce Animtor clientele which is exacly what would happened if it did. It was also waste developement resources. It shouldn’t supersede animator with shaders, and lighting effects. EIM should be rolled into Animator anyway, so render output module shoudl not be a priority. Instead, Camera should render from any app and CCN files should be editable text file like a rib.

edit: Or would you just be happy with EIM as it was in the last incarnation, with bug fixes, but as UB.

AVT: Yes and slate it to be merged in Animator, so vertex editing can be addressed. We can even color a poly a different color in the same model.

We want to hear from you.

AVT: Well that’s all I have to say for now. That’s off the top of my head. EIA is a great app. It should be improve with some current industry conventions and features. Make it hot then move to EIM. When they are merge then it should be a whole new app.


#42

EIM was a great modeling application with an excellent GUI.
The hidden away SDS toolset (Ubermesh) was well ahead of its time and even tho ‘unfinished’ was very intuitive and remains unsurpassed, the feature list is a tad inadequate tho.

If EIM is not integrated into EIAS, then the sds (Ubermesh) toolset should be.

There is no way that without this foundation for character animation in EIAS, that properly designed deformation, bone driven morphs or selection set editing at vertex level, can be successfully or competitively implemented. Modern sophisticated character models are much more demanding of deformation correction.