The more I use Aurora Viewer the more I like it. I may be like Bandor Tyrell (the Debauchery brand in SL) and not go back to Firestorm Viewer. His video where he reviews Aurora Viewer is on YouTube. He does a great review of Aurora weather.
At first many think Aurora is just another viewer recompiled from Firestorm with things moved around and one or two new things or things done differently. But Aurora is a rethink of the viewer from the ground up. As I use viewer features I am familiar with, from other viewers, I find there is twist in them or something added. And some features are missing. But in the few days I have had Aurora it has updated 4 times (0.9.10 to 0.9.13). They are quickly adding stuff.
Aurora Viewer’s Director
With the release of v0.9.12 Director is fully functional… not that way. But it works. Writing about what and ‘how to’ it does its thing is a PITA. So, I made a video.
I took a couple of days making it. I experimented with Aurora a lot. I learned a lot. But… I don’t know it all. I just wasn’t patient enough to try EVERYTHING. But, I got a good start. I hope my tutorial helps.
Yeah the splash screen is AI generated. I gave it an image I made to model from.
I used an AI voice. It is too noisy where I was working. Both come from Grok.
The video is mostly from Aurora v0.9.12. The rest of the details, if you are interested, are in the video’s credits.
Viewer Launch
When starting Aurora for the first time and after updates I see a ‘compiling shaders’ message. Is this a Rust Language thing?
AI: No, it isn’t a Rust thing. Rust programs are compiled to a normal Windows .exe before you download them, so the viewer isn’t compiling its own code when it starts. The “compiling” step is almost certainly the viewer preparing graphics shaders for your GPU.
What’s actually happening
Aurora draws with wgpu on Vulkan, and its shaders are written in WGSL. Those shaders can’t be shipped already built for your card, because each GPU and driver needs its own machine code. So, on launch: [github]
- wgpu translates the WGSL shaders into SPIR-V, the format Vulkan uses.
- Your graphics driver (NVIDIA, for your RTX 4060) compiles that into native GPU code and builds the “pipelines,” meaning the combinations of shader plus render state.
- Aurora saves the results to disk. Its docs say it “keeps its own cache of compiled graphics pipelines,” so startup “no longer sits for twenty seconds on a black window when the graphics driver has emptied its shader cache”. [github]
So, the first launch, or the first one after a viewer update or a GPU driver update, should take the longest. After that it should be quick, because it loads from the cache.
Other viewers do this too
The LL viewer and Firestorm also compile shaders at startup. They use OpenGL GLSL, and the driver’s hidden cache usually makes it fast enough that you never notice. Aurora shows you the step and keeps its own cache, so it doesn’t depend on the driver’s cache still being there. Many Vulkan and DirectX 12 games also show a “compiling shaders” screen for the same reason.
One exception
If you built Aurora from source with cargo build or cargo run, the “Compiling …” lines in the console are real Rust compilation. The project notes that the first build takes a few minutes, and later builds only rebuild what changed. That only happens with the source build, not the installed viewer. [github]
If you see the message on every launch, even with no viewer or driver update in between, the pipeline cache probably isn’t being saved. Check the viewer’s log for a cache write error.
Scroll Bars
These behave differently than in most Windows apps. Usually you click in a blank portion of the scroll bar and the screen or list moves up or down one screen. In Aurora Viewer if you click 25% of the way down the bar, the screen or list pops to 25% of way down. Makes for moving through things much faster.
It is a surprisingly annoying experience but for you figure it out.
Me: Find tutorials.
AI: **No dedicated tutorials exist yet.** The Aurora Viewer’s **Director** is a very new machinima/camera-path tool (introduced in 0.9.10 around mid-November 2026 and expanded into a full tool in 0.9.11, released 17–18 November).
Me: So, I made my own.
Photo and Video Saving
Before starting the setup for video recording be sure you select where you want your snapshots saved. Do that by opening the camera. You can use the icon in the bottom menu or press Ctrl-Shift-S.
The Director – is what!?!
It is a built-in camera-track and film tool for machinima. Key capabilities include:
- Keyframe camera paths on a timeline (with Bézier handles visible in-world)
- Ready-made shots (orbit, dolly zoom, crane, tracking, push/pull, fly-over)
- Recording a hand-flown camera path and converting it to keyframes
- Per-keyframe settings (animation, lens/aperture/focus, time of day, lock-on-target)
- Move/rotate handles on cameras in the world (using the same-style handles as the IK tools)
- Playback of the track (world-only view)
- Offline rendering up to 4K (or PNG sequence) at fixed frame rates (24/25/30/50/60/120 fps), with fades, titles, photo-mode filters/LUTs, and optional sound muxed via ffmpeg
- Track library (save/load/import/export) and simple montages of multiple tracks
- One-click ffmpeg download if it is not already present
It is accessed from the bottom toolbar (Director button next to Photo) or
Top menu → World → Director.
The feature is only a couple of days old in its supposed complete form, so user-made tutorials (YouTube, Primfeed, forums, etc.) have not appeared yet. Checking the Discord or the GitHub issues/discussions is currently the fastest way to get practical walkthroughs or ask questions.
You can get to the Discord channel from the viewer or website.
There are limits when using Director. I ran into them making this video. The most serious is not being able to record editing the camera track using Aurora’s recorder. Turn on Record and it hides the track/path I want to edit. I had to resort to Windows’ Snipping Tool to record the editing.
If you are a OBS user… disappointment. Aurora and OBS running together lags my i7 260 running at 5.2GHz with 64GB and a RTX 4060 to a crawl. It can take 30+ seconds for windows to respond. Unusable. Thus, I resorted to the Windows Snipping Tool to capture some of the video.
Link to next page, below…