Twilight Render for Mac - beta testers wanted
-
We are looking for people to test the soon to be released Mac version of Twilight Render 1.5!
Testers must:
- be licensedusers
- run OSX 10.6 or later on an Intel (x86 or 64bit) machine
- be willing to assist developers in diagnosing problems by sending examples of problem scenes, providing clear, detailed descriptions of how the problem was caused
*Preference given to users who have contributed constructively to the Twilight Render forum community.
Please post at the Twilight Forum here if you are willing and eager to help out! We appreciate all the help we can get in rolling out the Mac version of Twilight Render 1.5
-
-
-
@frederik said:
(was that so hard to figure...?)
Yes, it is confusing...it could have meant licensed users of Sketchup.
...another strange thing is why would you be a licensed user of Twilight if you are a Mac only user, and there has been no Mac version til now??Anyway, congrats on the upcoming Twilight for Mac release!
-
@frederik said:
@unknownuser said:
of?
Twilight Render - of course...
(was that so hard to figure...?)not really..
the 'of?' comment meant more than what it says on the surface. -
@d12dozr said:
@frederik said:
(was that so hard to figure...?)
Yes, it is confusing...it could have meant licensed users of Sketchup.
...another strange thing is why would you be a licensed user of Twilight if you are a Mac only user, and there has been no Mac version til now??Anyway, congrats on the upcoming Twilight for Mac release!
Yes, I've looked forward to this. I can understand how beta testers who have used the program in windows will be more useful to your evaluation. Of course they are all dual platform users.
-
@pbacot said:
I can understand how beta testers who have used the program in windows will be more useful to your evaluation.
sort of..
then you end up with an app that behaves like a windows app but it happens to work on mac..
that's what i like about the mac rhino beta.. they're seemingly more interested in feedback from mac users that have never used the windows version before.. they're trying to make rhino a true mac app..
all this aside, i don't mean to sound negative or unappreciative for the twilight team's efforts.. of course, i'll always welcome more rendering solutions on mac
-
Always last to the party.
-
That is exactly what I hate about Mac for Rhino. Developers instead of porting great GUI are now changing it . It is almost new application now. It will end up badly...Just look at the AutoCad for Mac . It is completely new software....useless if you work cross-platform.
-
@sepo said:
That is exactly what I hate about Mac for Rhino. Developers instead of porting great GUI are now changing it . It is almost new application now. It will end up badly...Just look at the AutoCad for Mac . It is completely new software....useless if you work cross-platform.
right, i understand what you're saying re: cross platform users.. i suppose in that situation, you'd want both of the apps to be more or less identical..
from a developers/business standpoint, that might not be the best way to look at it though.. I mean, if someone has a windows license for rhino then a mac version becomes available which the user would prefer, they would more likely than not, just transfer their license to mac (i.e.- no new business)from a diehard mac user point of view (and i don't mean apple fanboy.. just people that are completely used to macs etc.), the apps that are straight ports just look bad and generally aren't very popular on mac (kerkythea comes to mind.. i think i opened that app once or maybe twice and never went back
)so for mcneel to do what they're doing with mac rhino, i think, is a smart move.. their windows based users just won't use the mac version if they don't find it appealing.. but they won't be losing any business over it.. while at the same time, they're creating a true mac app which will attract many more mac people than a straight port would.. (i.e.- an entirely new user base.. thousands of new licenses)..
-
Kerky isn't a full mac app anyway, like GIMP. (I just wish GIMP had Mac commands-- and there's also the terrible save interface). Isn't SU or PS a better example? There are fewer dissimilarities-- and more the capabilities and lack thereof for each platform. Why does someone want to work in two platforms on the same app anyway?
-
Hmm, so I have a twilight license, but no Mac?
So who exactly are you looking for to test this? Jeff makes a great point - if you are making Twilight for Mac - wouldn't you be looking for a totally new user base - I don't think you'll be converting a whole lot of current windoze users. -
No you would not want to convert people but there are people who run windows version on their mac and they would wish to move to mac side.
In my case I teach Rhino and I am finding that even mac users are moaning about mac version not being the same is confusing. I repeat look at the shambles of auto ad for mac. On the other hand look Vectoworks which looks same on both platforms ...real joy. -
@sepo said:
No you would not want to convert people but there are people who run windows version on their mac and they would wish to move to mac side.
In my case I teach Rhino and I am finding that even mac users are moaning about mac version not being the same is confusing. I repeat look at the shambles of auto ad for mac. On the other hand look Vectoworks which looks same on both platforms ...real joy.well, vectorworks went mac -> windows instead of windows 1st
most of the moans on mac rhino so far (that i'm aware of) is lack of commands etc being hooked up.. marlin has barely even scratched the surface regarding the UI for mac rhino.. once he gets to that phase (cashmere), i think a lot of the moans will cease.. at this point, they're just getting everything hooked up and running smooth (and v5 is still in beta even on the windows side)… once v5 is released, i think we'll see a lot of improvements re: the UI.
basically, photoshop is the best as far as dual platforms go.. but they coded almost everything , including the toolbars, where as most apps just tie into what's available via the OS.. it takes a giant company like adobe to pull that off though.
-
but hey.. twilight mostly works inside of sketchup, right?
if that's the case, then everything should be A-ok because for the most part, sketchup is nice and mac-like on mac...
you can do most of indigo's setup inside of sketchup to which is good.. once you're in the actual indigo app, on mac, things start looking/acting weird… but since i don't have to spend much time in the actual app, no biggie..
-
@unknownuser said:
but hey.. twilight mostly works inside of sketchup, right?
if that's the case, then everything should be A-ok because for the most part, sketchup is nice and mac-like on mac...
you can do most of indigo's setup inside of sketchup to which is good.. once you're in the actual indigo app, on mac, things start looking/acting weird… but since i don't have to spend much time in the actual app, no biggie..
I really do not care for that so called mac look . I just do not want to go and spend uneccessery time learning new GUI for the sake of it. If something works than it something works. Also I can,t see developers are gaining anything but making two different sets of GUI.... Sorry but I see it being irrelevant. If it works do not brake it .
The point of Vectorworks is not where it was ported first but that it is the same...
-
@sepo said:
I just do not want to go and spend uneccessery time learning new GUI for the sake of it.
right.. that's exactly the point i'm getting at…
on mac, all the apps are more or less the same UI (or can be)…
i can use safari, then keynote, then sketchup and everything is more-or-less the same look/location/shortcut/function/etc (when applicable)
so when i open some app with a wonky (well, you might think it's a great UI but..) GUI then it's a turn off..
like this:
ugh.. no thanks.. i don't want to learn an entire new interface just for the sake of rendering.. if they set thea up using a more standard mac interface then it'd be much more welcoming..
-
@sepo said:
Also I can,t see developers are gaining anything but making two different sets of GUI.... Sorry but I see it being irrelevant. If it works do not brake it .
what the developers have to gain from it is more sales… believe it or not, there are actually a hellofalotta people using macs these days.
using thea again.. for me to use thea, not only do i have to learn how to use the parameters etc, i basically have to re learn how to use a computer in general.. the latter, to me, is much more unwelcoming than the former..
so the thea devs are probably sitting around thinking "see, we made this mac port but barely anybody is using it.. therefore, macs are still irrelevant" (or whatever).. when in reality, a lot of mac users have looked at it and don't want to use it because it's not a mac app.. if it were, then i bet it'd be much more popular on mac.
going into a mac port with the idea "hey, this is a great UI on windows so we'll make the mac version the same.. And hey, mac UI is stupid so we aren't going to make it like that" (or whatever) is just shooting yourself in the foot.. while i understand you may like the windows UI, i and many others don't and that's why we don't use windows to begin with..
-
What exactly is so un-Mac about Thea?
Looks fine to me?
-
Jeff, not sure what your point about Thea is - I see the same (imo bad) interface on Windows - that has nothing to do with Mac. Having to learn a whole new GUI is what turned me off of Thea too. The Twilight interface on the other hand is simple (if limited in functionality) and well integrated within Sketchup. If they are able to bring that simplicity to Mac, everyone should be happy.
Advertisement