Modo coming to linux?
interpolator
Saw this on facebook, posted by Luxology modo page:
Caption is: Like penguins?
If modo comes to linux, and if xnormal 4 does too, then we will certainly be living in interesting times. I'd love to be able to move to linux but obviously there's a lot of programs that would need porting to linux (I doubt there are m(any) game-artists that use linux + blender or something at the moment), and drivers are still way behind, but this is a step in the right direction for me.
^ Terrible sentences because am excite.
Caption is: Like penguins?
If modo comes to linux, and if xnormal 4 does too, then we will certainly be living in interesting times. I'd love to be able to move to linux but obviously there's a lot of programs that would need porting to linux (I doubt there are m(any) game-artists that use linux + blender or something at the moment), and drivers are still way behind, but this is a step in the right direction for me.
^ Terrible sentences because am excite.
Replies
Man, Linux has been getting a lot of love from software developers lately.
I don't think it's aimed at personal users, though. Lots of biiig VFX houses run on Linux. Also makes for cheaper, faster, easier render farms, too.
Modos logo in Foundry style in bottom right corner! I know it's not a shocker but I'm interested what this fusion will bring to the table.
I completely beg to differ, and a month after switching you will too. Valve are bluffing for sure to try and maintain their desktop games monopoly in the face of having some actual competition for the first time in years. There's no way identical code would run so much faster on Linux than on Windows. Faster, maybe, but not by much. Wonder if they rewrote their Windows/DX renderer today using newer features and better architecture it'd go as fast. Probably would.
For goodness' sake, I have to hex edit EDID dumps to use my monitor's native resolution on my nVidia desktop, and the drivers on my ATi/AMD laptop are hilariously unstable. Everything from basic operations hanging the driver to some multimonitoring configurations misaligning screens and adding a line or two of static along the top/bottom. And it's been like that for a good two years now, I don't forsee it ever being fixed. No problems in Windows.
It's not a bad OS really, really quite cool for development, but for 3D in particular it just has far too many bugs all up and down the spectrum. Look before you leap.
last line of the special offers.
also you have some serious bad luck james, I havent had any of those problems with kde or Gnome.
Going up in price too it seems: "New licenses of MODO 701 will increase to $1495 and new floating licenses of MODO 701 will increase to $1795."
Just to clarify, Luxology wasn't bought out, they have gone into a partnership with The Foundry.
Actually, I think you'll find they merged - http://www.fxguide.com/featured/foundry-and-luxology-merge-fxg-exclusive/
Linux support is nice for those that use it, but to me the only things they've mentioned for 701 that sound interesting are:
-Schematic improvements, reducing scene graph complexity.
-Simplified complexity of materials and layered shaders
Will be interesting to see what they changed there. But honestly all I really want to see atp is a proper fix for the double-vert/edge/face problem instead of relying on the band-aid script "Mesh Cleanup". I pretty much had to hotkey that 'fix' last time I tried Modo because its modeling tools create broken geometry continuously no matter how you work. Fixes to the ever-broken symmetry would be nice too.
Totally feasible, but don't be surprised if you notice a lack of willing contributors that use the said free software.
Symmetry's sometimes a bit flaky but definitely not "ever-broken". It's not hard to fix it, either.
And maybe it IS a workflow thing but I have Seneca's fix mesh script bound to a key I can easily hit because I must hit it 50 times a day. It's not a huge hassle as it fixes whatever is wrong but, yeah, I hit it a lot.
For Symmetry, what I meant by ever-broken was that its had problems that have been with it for ages that never seem to get fixed. I've given Modo a shot every new version starting with 301 years ago, and Symmetry has remained consistently buggy through every version I've used.
Well, we have:
Blender 3D
Gimp
Audacity
Unity 3D/UDK/Cryengine/Blender engine Edit: Sauerbraten
That seems like plenty of software to get you started making games without spending a dime. You could even go fully Linux with Sauerbraten as your engine.
Warren... just tested and symmetry works for me across an altered workplane and across reference axes (hit the spot in the Items list beside your mesh item, it will align the world axes to the item's local axes, hit it again to go back to regular world axes)...
Im using Linux since SuSe Linux 6.0 soooo i seen a LOT, about the OpenGL performance i am not just talking about Valves engine even though at the current state is works a lot faster under Linux, ohh and btw Valve wrote a very nifty wrapper to translate a lot of there DX code to OpenGL so its kinda impressive that its not even 100% native Linux code and still works better.
Anyway back to topic, i played Quake 3 Arena on Linux back then and guess what, even back then it was faster at least 25 fps if i recall right. Current gen Ungine run about 3-6 FPS faster on my current hardware. Unreal Tournament 2004 always was about 10-15 FPS ahead, the original UT was kinda working crap back then. Maya was also quite a joy under Linux even though i have to admit Maya 7.0 was the last one i tried under Linux.
nVidia never gave me much trouble a few ubuntu releases i had to manually tweak the xorg.conf but since the quite a few version this is really gone for me.
Well and ATI/AMD they suck and will prolly always do i didnt even have a good time with there Windows drivers, again why i wont touch there stuff anymore, shame though good hardware in it self.
Multi monitoring ok thats also kinda an issue still but considering Wayland gets a heavy push and nVidia likely supporting Wayland natively soon as well this should be sorted in the future.
So all in all i would it call an useable OS for 3D, if enough software vendors gonna go to Linux, the driver issues will also be solved when nVidia and AMD see enough cash in Linux to bother.
From what I read nVidia has no interest in suporting wayland with its closed source drivers. Ubuntu has dropped support with their own Mir.
http://www.pcworld.com/article/2030053/with-convergence-in-mind-ubuntu-linux-scraps-wayland.html
I dont know what Modo plans to concentrate on, but since Valve has stated Ubuntu will be the initial port to work. While needing closed source drivers for the gpus full potential.
Wayland may be sol. Even if redhat will support it.
http://www.phoronix.com/scan.php?page=news_item&px=MTE5MTk
An older news about it but apparently some insider have heard nVidias interest has gotten bigger about this case lately.
ubuntu stands absolutely alone with Mir, all other distros will likely use Wayland, will be interesting to see however if nVidia will support Mir that might change the game. In any case this small war between Wayland and Mir might be useful (since both sides will do a lot effort to win out). Both nVidia and AMD have to either join Wayland or Mir sooner or later, because the big distros will use it either way sooner or later, Xorg is nightmare of code to maintain everyone in the Linux field knows that and how important a more modern, small and faster solution is.
Yeah, I'm sure this is true. I used Modo before Max, but now I've gotten so used to Max (and I don't use it at work), so I probably haven't given it enough time to relearn the way Modo wants me to work.
Yeah, that sounds wierd to me actually ^^ I dont know, I would like to see what it is people are doing that causes these things, because im not quite sure what it means ^^
I think a lot of folk who come over from Max get confused, Max is odd in that it very easily lets you make sloppy models (even the cut tool will show that you're cutting from a vertex, but will actually make a second vert right next to the one you've picked) but at the same time has quite stringent rules on what you can and can't do with a mesh.
Modo's sort of the opposite in that, as it doesn't have such stringent rules, it forces you to create very clean meshes.
I dunno, I've used modo since 101. I remember having those issues way back at the start, but back then sometimes the tools could mess up symmetry. I guess I've learned to keep very high standards of mesh hygiene.
Stucked with modo 302.
Kind of like Activision and Blizzard (in reality, Blizzard bought ATVI :P)
It's been there since, I think, 501. It's basically Seneca's script made official.
But I too have a key bound to the latest Seneca script because it does a few things that the menu one doesn't like unify the sub-d across a mesh and stuff like that.
Speaking of scripts, when I tried writing some simple context sensitive tools with Perl hardly anything worked. I asked support about it and they basically told me they had no idea what was wrong as there was nothing wrong with my code. So yea, Modos scripting has some issues too, at least with Perl.
What was the issue?