Skip to main content
Up and Coming
August 12, 2014

SDK 0.4.1 Released

"From my email" wrote:

The Oculus SDK v0.4.1 has been released!
You can download it now at https://developer.oculus.com/?action=dl.

Release Highlights

Added Mac OS support.
Added “Pause Service...” option to the Configuration Utility, allowing 0.3.x SDK applications to run.
Fixed various display driver bugs. Service no longer requires SSE4.1.
Fixed Unity Integration shadow support.
UE4 integration patch is now available that supports 0.4 SDK and runtime.


Make sure to update the firmware and all that good stuff. Gypsy beat me to the punch in the announcements section, though we can discuss the changes here 8-)

    20 replies

    New Participant
    August 12, 2014
    Dumb question, how do I view FPS under the World Demo? In .4.0 on Win it was just there under the main options window. On the mac it seems to be absent / hiding from me.
    Up and Coming
    August 12, 2014
    Hey iandanforth – If you press spacebar you should be able to view FPS and other info.
    Cubicle Ninjas Custom VR App Development Guided Meditation VR for Rift, Gear, and Go
    Honored Contributor
    August 12, 2014
    Am i right in saying there is no need to update the rift firmware if you has already updated on unboxing? (ie used with 4.0?)

    I havent tried yet but from what i have heard on other forums, in terms of performance, not much has changed

    is this what you guys are seeing? Apparently much of the stuttering in direct mode was meant to have been fixed I thought?*

    *obviously assuming your hardware is up to task
    Fiat Coupe, gone. 350Z gone. Dirty nappies, no sleep & practical transport incoming. Thank goodness for VR :)
    Up and Coming
    August 12, 2014
    Didn't bother updating the firmware, I just uninstalled the runtime and installed the new one. The service no longer needs the SSE emulation. :mrgreen: Now to wait for E:D to implement the changes...
    G3258 @4.4MHz GTX970 8GB RAM Windows 7 64
    Up and Coming
    August 12, 2014
    Good news: per another thread, an Oculus employee confirmed that there is no additional firmware update needed for 4.1.
    Cubicle Ninjas Custom VR App Development Guided Meditation VR for Rift, Gear, and Go
    Up and Coming
    August 12, 2014
    And an attempt to update existing 2.11 firmware over itself results in, for the moment, a totally unusable device. I'm worried I've bricked it as full restart still results in "Error Writing Firmware" error messages.

    If you already have 2.11 installed, don't try to update!!
    saviorntAuthor
    Up and Coming
    August 12, 2014
    It sounds like the firmware install corrupted or did not complete. Overwriting firmware on any device with the same version should not result in an unuseable device.. if this is the case with the Rift, that is a very big bug in the code that needs resolved asap.

    Have you contacted Oculus dupport yet? If not, do it.
    Current WIPs using Unreal Engine 4: Agrona - Tales of an Era : Medieval Fantasy MORPG
    Up and Coming
    August 12, 2014
    I just submitted a ticket. Hopefully, someone will notice.

    Here's the full text for others, below:

    With the release of the 0.4.1 runtime and SDK, I went to install the newest firmware as the release notes said to do so.

    The configuration utility told me I already had the 2.11 installed, but I thought, well, the release notes say to make sure to update, so I guess I'll install it again.

    This results in an "Error Writing Firmware" error and listing the model in the configuration utility as "Boot Rift DK2."

    I have restarted multiple times, but any attempt to update the firmware further results in the same "Error Writing Firmware" error, with different address blocks given as the position.

    What should I do?
    Up and Coming
    August 12, 2014
    "EvilJordanChiat" wrote:

    The configuration utility told me I already had the 2.11 installed, but I thought, well, the release notes say to make sure to update, so I guess I'll install it again.


    I guess "if needed" was implicit...
    Up and Coming
    August 12, 2014
    "elect" wrote:
    I guess "if needed" was implicit...


    I was just following directions! But, to be fair, one shouldn't be able to overwrite the same firmware version, and if one could, it shouldn't result in an error.