![]() ![]() This one is particularly annoying since I was planning to do most of the coding on my MBP, while tuning the graphics performance and benchmarking on PCs/mobile devices. I just give up on OSX and iOS support and write everything in Vulkan. This will simply mean that some options won't be available on mobile, which is fairly sad because these features are supported though Metal, ES 3.2 and Vulkan. I use OpenGL 4.1 on desktop and ES 3.0 on mobile, while giving up on cross-platform tessellation and geometry shaders. Unfortunately, this means having a way of writing shaders that works on both APIs, but that shouldn't be the biggest issue. This way I would use tomaka's vulkano and write some Metal wrappers and have this work on virtually every platform. Basically, an abstraction that lets you implement performance-oriented real-time renderers with a lot of room for post-fx. ![]() ![]() I write a wrapper around Vulkan and Metal that will provide exactly what I need for the engine. The way I currently see it, is that I have three options: So using ES 2.0/3.0 everywhere will not work. Something that I should probably mention is that I want to have tessellation support. Considering that OSX is still running on OpenGL 4.1 which was released in 2010 (that is almost 6 years ago), I can't really be assured that they will actually implement Vulkan on their products. Vulkan sounds absolutely awesome until you realize that Apple hasn't said a word about supporting it. The obvious problem is the absolute havoc that's happening between the big companies and the graphics APIs. I'm trying to wrap my head around how to actually make a decent cross-platform game engine that will support Windows, Linux, OSX, iOS & Android. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance. Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |