Ramses – A distributed system for rendering 3D content
github.com
github.com
Nothing here: https://www.youtube.com/results?search_query=bmw+ramses
# Example
In a very simplified example, a client instance (e.g. the Navigation process) will create a 3D scene and "publish" it within the connected RAMSES applications (e.g. the renderer of each HMI).
These renderers will "subscribe" to the published scene and show it on the screen.
So not just for the giant grids you see at CES. But also applicable to thin clients, LAN party play, art gallery installations, etc.I thought cables are short enough in a car that they can attached the displays directly to rendering hardware. Are there other advantages? Provide a fallback in case one render process fails?
The network simplifies the wiring and reduces the amount of wire used. Material cost reductions across the life of the car (from design to use).
In a very simplified example, a client instance (e.g. the Navigation process) will create a 3D scene and "publish" it within the connected RAMSES applications (e.g. the renderer of each HMI).
These renderers will "subscribe" to the published scene and show it on the screen.
I am fascinated by such systems. In the best case you get screen/tmux re-attachment features for GUIs, down to the application level, not desktop level (x11/xpra does some of this). And you do not just stream pixels across a network (like x11) but have at least some of the render logic locally. If you can then use local graphics hardware that seems like an unbeatable combination.
Maybe some websockets/webgl/webassemly which does all that will become the de-facto platform agnostic GUI platform in the future.
But this looks neat as well, I did not know that one nor found it during my search.
By the way, if your company is in desperate financial difficulty, circling the drain with increasing speed, and the management cobbles up a "save the company" project and they name it "Falcon" it is WELL past time to polish your resume and bug out. I've seen that code name several times, and it's spelled utter doom (two bankruptcies and one buyout that was worse than going bankrupt).
In my head the conversation goes something like this:
----
[Int. meeting of High Management]
MARKETING HONCHO: "This is it. We're going to save the company with this new product. We're calling it Project Phoenix. Rise from the ashes! When can engineering start?"
ENGINEERING DIRECTOR: "Uh, don't Phoenixes burn themselves to death? Isn't that kind of a negative thing? The teams are a little burned out from the last save-the-company death march."
"You have a point. Let's call it something like . . . Fee-- no, um, Fun--, no . . . um, Falcon. That's it. Project Falcon."
"I guess that's better."
"Go save the company."
"Right. I'll just pop down to engineering and cancel all the vacations. When can you tell us about the product?"
"Later, when we decide what color it should be."
----
I have insufficient data, so it's possible that any project named after a large bird is bad juju. Stay safe :-)
PayPal and U.S. Bank have internal tools named Fusion. (I want to say that Cisco Systems does too, but I can't remember for certain.) Oracle, VMWare, and Autodesk all have products named Fusion (Fusion Applications, VMWare Fusion, and Fusion 360, respectively). IBM has two products named Fusion (Fusion Commerce and FusionAnalytics). Google used (naturally) to have a product named Fusion Tables.
What did I miss?
Let's try General Motors:
https://github.com/GeneralMotors
Yep, that is empty.
"The GENIVI Alliance is a non-profit automotive industry alliance committed to driving the broad adoption of open source, In-Vehicle Infotainment (IVI) software and providing open technology for the connected car. The GENIVI Alliance was founded on March 2, 2009 by BMW Group, Delphi, GM, Intel, Magneti-Marelli, PSA Peugeot Citroen, Visteon, and Wind River Systems"
I'm looking forward to seeing more of the technology working in the AV space get opened.