![]() Believe it or not, but 99% of the blood community including TF devs believe that one of the greatest downsides of having to use the Darkplaces engine is dynamic lightning because it: a) looks and feels nothing like sector shading b) screws up the appearance of walls and models because colored lights interfere with the palette. Half of BLOOD's charm was in it's grittiness and moody palette - the 'eye candy' could be attractive to non-fans and people who think that dynamic lightning would actually be an enhancement. ![]() Many even refuse to set the resolution anywhere higher than 640x480 or 320x200 even though it's supported. I used to think that switching to Q3 engine would be a smart move but some devs who have had more experience with it, showed me otherwise.ĭespite the popular belief, BLOOD fans don't care about 'eye candy' at all. That option was discussed and has been overruled because it would arouse many difficulties. I think there is a 'freeware' version of the Unreal engine that can be used for non-commercial projects. If that is the case, there is always the Q3 engine, which is now open source as well. Oh wait, that's already happening - except that 3D Realms actually cares to protect their IP and noone gives a damn if the game is coming from the outside. Otherwise you would have any monkey on the face of the Earth giving themselves rights to rip the content from BLOOD or Duke3D and making their own mocks of the game and some such abominations. Not even a 'blessing' would do - especially not from Monolith. You don't do things based on what someone said or what someone thinks is ok to do further based on some hearsay. OS X MOUNTAIN LION CRASH LICENSEIt was Infogrames that supposedly issued a license to the qBlood team to use the content. Because you see, it was not up to Monolith to give blessings or they ever did anything of sorts. If you say breaking the law is justified because someone claims to have connections with Monolith then I can only tell you that you're being hilarious beyond taste. I believe Hudson has contacts and I think you're trying to hide your envy behind sarcasms :pīut hey, official blessing from Monolith would be nice. ![]() 5.x: Sibelius 5 Crashes after opening in M. Posted by Lindsey Lambson - 13 Aug 10:32PM (edited 13 Aug 10:33PM) 5.x: Sibelius 5 Crashes after opening in Mountain Lion OS X MOUNTAIN LION CRASH MACBut that's not what I really expected as I am a passionate Mac user. I'm afraid the only way to get working Sibelius 5 on Mountain Lion will be using a virtual machine running Windows. However, aside from the above issues, you should find that it runs without significant problems." So I upgraded to Mountain Lion without any concern - but not being able to use playback in Sibelius is undoubtedly a "significant problem" in my opinion. OS X MOUNTAIN LION CRASH MAC OS XJust to compare, other software companies provide updates for much older products.įurthermore, I'm always cautious before upgrading an operating system, so I looked up and found that article in the Avid Knowledge Base saying: "Sibelius 5 is not officially supported on Mac OS X 10.7 Lion or 10.8 Mountain Lion, just as it is not officially supported on Mac OS X 10.6 Snow Leopard. Of course I can imagine that fixing this playback/mixer issue is not as trivial as it seems, but I am profoundly convinced that updates for a "premium" software product like Sibelius shouldn't terminate not even 5 years after release. ![]() ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |