Red Desert Render Mac OS

1. Red Desert Render Mac Os 11
2. Red Desert Render Mac Os X

1. Render Shift: Maxon's Redshift for macOS Debuts - CGW explores how leading-edge graphics techniques, including the 3D modeling, animation and visualization are used in such applications as CAD/CAM/CAE, architecture, scientific visualization, special effects, digital video, film, and interactive entertainment.
2. Font rendering in Mac OS X. On Mac OS, all browsers use the Quartz rendering engine. TrueType and PostScript fonts are rendered in exactly the same way, since hinting—the biggest conceptual difference between the two formats—is ignored. The subpixel rendering on Mac OS is very robust, so this platform is typically the one we need to worry.

Originally posted on 13 April 2021. Scroll down for news of native support for M1 processors.

Maxon has officially released Redshift for Mac, the new macOS edition of Redshift, its GPU renderer.

This article was written by Chiara Corsaro.Chiara Corsaro is the General Manager and Apple Certified Mac & iOS Technician for macVolks, Inc., an Apple Authorized Service Provider located in the San Francisco Bay Area. Was founded in 1990, is accredited by the Better Business Bureau (BBB) with an A+ rating, and is part of the Apple Consultants Network (ACN).

Native support for Apple's Metal graphics API is available in Redshift 3.0.43, the current production build; support for Apple's new M1 processors will follow after the release of macOS 11.3.

Updated 30 April 2021: Native M1 support is now available in Redshift 3.0.45.

The changes make it possible for users of host apps that run on macOS – now including Blender, Cinema 4D, Houdini and Maya – to use the renderer on current Mac laptops and workstations.

Native support for Apple's Metal API makes it possible to run Redshift on new Macs again
First rolled out as a public beta last year, the port from Nvidia's CUDA to Apple's Metal as a GPU computing API will enable Redshift to run properly on current Mac hardware.

Apple no longer supports Nvidia cards, even as eGPUs, and in any case, CUDA no longer supports macOS.

To run on Macs, Redshift currently requires macOS 11 Big Sur, and either an AMD Navi or Vega GPU, AMD's current- and next-generation graphics cards.

That means a machine less than three years old: Navi GPUs first became available in Mac desktops in late 2017 with the iMac Pro, reaching Mac laptops the following year.

Red Desert Render Mac Os 11

You can see a full list of supported GPUs here.

Native support for M1 processors to follow ‘in the next few weeks'
While Metal support is available today in Redshift 3.0.43 – according to the Redshift Trello board, it's actually been available since version 3.0.38 in February – anyone with a really new Mac will have to wait a bit longer.

Although Maxon is working on native support for M1 chips, the first of the new Apple Silicon processors, which rolled out late last year, it won't be available until Apple releases macOS 11.3.

Updated 30 April 2021: Native support for M1 processors is now available in Redshift 3.0.45. Compiled binaries of the software are available for both AMD and M1 Macs.

You can see an overview of the other new features in the update on the Redshift Trello board.

Pricing and system requirements
Redshift 3.0.45 is available for 64-bit Windows 7+, glibc 2.17+ Linux and macOS 11.0+. It costs $500 for a node-locked licence; $600 for a floating licence.

The renderer's integration plugins are compatible with 3ds Max 2014+, Blender 2.83+, Cinema 4D R17+, Houdini 17.0+ (18.0+ on macOS), Katana 3.0v1+ and Maya 2014+ (2016.5+ on macOS).

Read Maxon's announcement of Redshift for Mac

Apple no longer supports Nvidia cards, even as eGPUs, and in any case, CUDA no longer supports macOS.

To run on Macs, Redshift currently requires macOS 11 Big Sur, and either an AMD Navi or Vega GPU, AMD's current- and next-generation graphics cards.

That means a machine less than three years old: Navi GPUs first became available in Mac desktops in late 2017 with the iMac Pro, reaching Mac laptops the following year.

Red Desert Render Mac Os 11

You can see a full list of supported GPUs here.

Native support for M1 processors to follow ‘in the next few weeks'
While Metal support is available today in Redshift 3.0.43 – according to the Redshift Trello board, it's actually been available since version 3.0.38 in February – anyone with a really new Mac will have to wait a bit longer.

Although Maxon is working on native support for M1 chips, the first of the new Apple Silicon processors, which rolled out late last year, it won't be available until Apple releases macOS 11.3.

Updated 30 April 2021: Native support for M1 processors is now available in Redshift 3.0.45. Compiled binaries of the software are available for both AMD and M1 Macs.

You can see an overview of the other new features in the update on the Redshift Trello board.

Pricing and system requirements
Redshift 3.0.45 is available for 64-bit Windows 7+, glibc 2.17+ Linux and macOS 11.0+. It costs $500 for a node-locked licence; $600 for a floating licence.

The renderer's integration plugins are compatible with 3ds Max 2014+, Blender 2.83+, Cinema 4D R17+, Houdini 17.0+ (18.0+ on macOS), Katana 3.0v1+ and Maya 2014+ (2016.5+ on macOS).

Read Maxon's announcement of Redshift for Mac

Tags: 3ds max, AMD GPU, Big Sur, Blender, Cinema 4D, CUDA, GPU rendering, Houdini, integration plugin, Katana, M1, M1 processor, Mac, Mac mini, MacBook Air, MacBook Pro, macOS, macOS 11.0, macOS 11.3, Maxon, Maya, Metal, native M1 support, Navi, new features, Nvidia GPU, price, production renderer, Redshift, Redshift 3.0.38, Redshift 3.0.43, Redshift 3.0.45, Redshift for Mac, Redshift for macOS, Redshift for Metal, Redshift Rendering Technologies, release date, rendering, supported GPUs, system requirements, Vega

This wiki describes how to use the stereo vision or anaglyph images ability of OpenSceneGraph and let you experience the FlightGear world in 3D. Another excellent example and simple application of FlightGear's flexibility and realism.

Important Notice: Even though it might not pose any danger, try avoiding excessive use of different color paired glasses, and after your flying sessions with the glasses or whatever, let your eyes and brain rest for a while before starting to sew, chop meat, drive 160mph, dig the garden etc.

Anaglyph, that weird looking glasses...

As you might know or not, FlightGear migrated graphics functions from PLIB to OSG. FlightGear 1.9.0, released December 22, 2008, marked the release of the OSG version of FlightGear. As of August 2010, most recent stable version of FlightGear uses OSG. For those who are unaware of OSG, it is an open source high performance 3D graphics toolkit.

Stereo vision exploit the human perception by showing a 3-Dimensional image on a 2-Dimensional surface. To understand stereo vision and human judgement of visual distance (that is how we keep visual separation from the traffic), make the following small experiment. While reading this text, close your left eye and then right eye, open left. When you alternate your view, it'll feel like the monitor is moving to little left when you observe with right eye, and vice versa. This situation gives us two different images. Now imagine you took this two 'slightly' different images and match it such that each eye sees what it is supposed to see. There are not so many but quite a few ways to achieve this separation. And OSG is capable of doing all of this. Now apply this to your short final 28R at KSFO!

How to multiply your realism level by 10

For this experience, you will need

1. A working copy of FlightGear, of course.
2. A pair of Red-Green or Red-Cyan pair of 3D glasses. You might have one at home or if you are a DIY type, check NASA way of doing glasses or Liquid Crystal Shutter Glasses and probably suitable hardware (anyone experienced with or owns one pair of this thing might help developing this page).

Versions later than 2.0

Versions later than 2.0 (including Git sources) have native support for setting the relevant properties at runtime from a dialog box at View > Stereoscopic View Options.

Windows & Linux

FlightGear launcher

1. Start the FlightGear launcher, select your aircraft and select your location.
2. On the next screen, click 'Advanced' just above the 'Run' button.
3. On the new window, titled 'Advanced Options' highlight the 'Environment' from the list on the left
4. Now, you will create new environment variables, click 'New' and type OSG_STEREO=ON, then again click 'New'. At this point you should be seeing 'OSG_STEREO=ON' on environment list.
5. The commands (including the one we just created) that you have to pass to OSG consist of:
   • OSG_STEREO=ON
   • OSG_STEREO_MODE=ANAGLYPHIC
   • OSG_SCREEN_DISTANCE=0.7
   • OSG_EYE_SEPARATION=0.06
   • OSG_SCREEN_HEIGHT=0.19
   • OSG_SCREEN_WIDTH=0.33

The result should be something like shown on the right.

After you entered the last value, click 'OK' to quit from the Advanced Options window. Remove your pilot raybans, put your fancy 3D glasses and click 'Run'.

Command line

When launching FlightGear from the Command line, the environment variables should be set as follow, in the same Command Prompt window (same batch file if applicable) as the one used for FlightGear.

Mac OS X

Thanks to someguy (not some guy, a FlightGear forum member!) for providing Mac OS X instructions. And here is the related postwith more screenshots.

1. In the Finder, select the menu item Go > Go to Folder... and enter '~/.MacOSX' without the quotes. You will go to a hidden folder in your user directory.
2. You should see a file named 'environment.plist'. Open it in TextEdit.
3. Between the and tags, add the following:

Don't disturb anything else in there and save the file. Then log out (Shut Down and Start up, or Restart). Fire up Flightgear and be amazed.

If you don't see environment.plist, you'll need to create it. No problem, just open a new document in TextEdit (or another .xml editor e.g. Taco), enter these lines, and save as environment.plist:

Tweaking The View/Stopping Nausea

A brief explanation of the values we gave for the environment variables goes like this. This info comes directly from the OSG Stereo Settings page.

OSG_STEREO=ON: is quiet self explanatory...We have to tell OSG to turn on the stereo rendering.

OSG_STEREO_MODE=ANAGLYPHIC: Well, the fanciness level starts here...In our relatively cheap case, we chose anaglyph rendering since we only had red-green or red-cyan glasses to see...So we tell OSG to fit our budget by rendering the scene according to ANAGLYPH method. But on the other hand, OSG provides not only ANAGLYPH (as default), it supplies its user with a wide variety of stereo render options.(Don't get scared by the frame rates shown on the screenshots, enabling stereo view didn't effected the framerates of the old laptop the screenshots were taken).These are;

• ANAGLYPH Use anaglyphic stereo when in stereo (default) (See green-red filtered images).
• QUAD_BUFFER Use quad buffered stereo when in stereo.
• HORIZONTAL_SPLIT Use horizontal split stereo mode when in stereo Starting,Running!, External Stereo View
• VERTICAL_SPLIT Use vertical split stereo mode when in stereo Vertical Separation Cockpit and External View

(Any practical application sample of Vertical Split?)

To understand the red-green images, one can carefully inspect especially the horizontally separated images. If you carefully look at this image, note how the runway markings are appearing in a different perspective in left and right images. This is an exact (but not working in this case) copy of 'cross eyed 3D' pictures.What OSG does when you tell to enable the Anaglyph instead of this horizontal stereo, it applies color filters that exactly (not at practice sometimes, within color bandwidth limits) matches with your green and red filters on your glasses. Then it overlaps these filtered images and displays as a single image. Then, your left eye, with a green filter, filters the green image and sees the reddish image and vice versa for the right eye. Thus, giving each eye what they should be seeing in a real cockpit is also assembled by our brain, and perceived as a 3D environment. A small reminder about the Quad Buffered Stereo. It should only be enabled when you have a proper hardware, such as liquid crystal shutter glasses. The author attempted enabling this command on a laptop, resulting in bunch of error log in FlightGear console window and application hang.

OSG_SCREEN_DISTANCE=0.95: is the 'distance' to your very own screen in metrics. For a good practice, you'd better measure this distance to your screen and not to make it 0.2 meters or 14.3 meters , since the first one is dangerous to your health and latter one to your flight profile. For multiple display, the measurements (should?) be from your viewpoint to the monitor surface. Contributes to the feeling of the depth on your screen.

OSG_EYE_SEPARATION=0.06: Eye seperation...Funny but is the actual distance between two pupils of your eyes. Measure but don't pop them out for a precision measure with a caliper. Makes significant contributions to the realism of the simulator. Generally 5 to 7 cm (0.05 to 0.07 meters). For imperial units convert 1 inch=25.4mm, 1 meter=3.280 ft.

Red Desert Render Mac Os X

OSG_SCREEN_HEIGHT=0.19: Is another basic measure. You can omit this and OSG will assign a default value, but of course, every monitor might be slightly different then the rest. This is the actual height of the visible image size on your screen.

OSG_SCREEN_WIDTH=0.33: Similar to the height. If you are really lazy to measure your screen dimensions or stuck in the middle of a desert with a laptop and internet connection, but no ruler and you don't have any idea of your handspan, here's another unlimited service from FlightGear!

Eye Separation and Horizontal Distance

The very final part of the OSG stereo view options consists of few variables that accommodate the device specific issues and finally allows you to set straight look or cross-eyed look (not advised) options. OSG_SPLIT_STEREO_HORIZONTAL_SEPARATION: variable adjusts the distance between two horizontally separated view-ports (e.g. right/left screens). If not specified in the environment variables with the OSG_STEREO_MODE=HORIZONTAL_SPLIT set, it takes its default 42 pixels value. This value is probably specific to the 3D LCD glasses (like tiny screens in front of your eyes), to adjust the distances between two images.

OSG_SPLIT_STEREO_HORIZONTAL_EYE_MAPPING: While OSG_STEREO_MODE=HORIZONTAL_SPLIT is set, it can take variables such as LEFT_EYE_LEFT_VIEWPORT or LEFT_EYE_RIGHT_VIEWPORT. LEFT_EYE_LEFT_VIEWPORT obviously set the left eye to render to left viewport, right eye to right viewport as a default if not set in Environment. On the other hand LEFT_EYE_RIGHT_VIEWPORT set the left eye to render to right viewport, right eye to left viewport (kind of cross eyed or again, device specific).

OSG_SPLIT_STEREO_VERTICAL_SEPARATION: theoretically does the same thing as horizontal separation but showing images up/down as opposed to left/right. It can take values similar to HORIZONTAL_SEPARATION in pixels.

OSG_SPLIT_STEREO_VERTICAL_EYE_MAPPING works the same way as horizontal mapping, displaying upper and lower images respectively. The string variables are LEFT_EYE_TOP_VIEWPORT and LEFT_EYE_BOTTOM_VIEWPORT, which are quiet self-explanatory.

External links