Update 9/8/2013: Test Build 01!
Get your fresh builds here!
Here’s how it looks now!
So what’s new?
Geez, a boatload. But offhand here are some new features:
- First pass at mission support! There’s now a simple mission you can playthrough that has a scripted set of events.
- Newtonian’ish physics (inertia with velocity caps)
- Afterburners & Shields
- Lots of new readouts on the cockpit monitors
- Initial pass at a pilot body
- Awesome docking bay/hangar to launch from
- Config tool for controller support
- Testing with multiple controllers (thrustmaster hotas, saitek x-52, logitech 3d extreme, xbox controllers)
- 4km diameter space station to fly around
- New asteroids, new asteroid explosions
- Around a dozen reworked sound effects
- "Look" based UI system for selecting objects and dismissing text windows
- Can now select friendly/neutral objects as targets (stations, waypoints, etc)
- Reworked rates of turn, speeds, firing rates
First Law - Test Build 00
What is this build?
This build is a very early build to let people play with the mechanics of flight and the basics of combat. It is not a game yet! But if you happen to have an Oculus Rift I hope you’ll try it and find some enjoyment out of flying your very own combat space ship. :)
Youtube video of latest build:
- Computer Specs: I have no idea, I’m using a 2011 macbook pro
- Xbox 360 controller
- Oculus Rift
- Headphones! The audio is a huge part of the experience
Instructions - Windows
You guys should be good to go straight out of the gates, no reconfiguration necessary. Enjoy!
Instructions - Mac
I haven’t found a way for Unity’s InputManager to know about the windows and mac key configurations, so the first time you run the game you’ll need to manually update the configuration. To do that:
- Start the game, a small runner dialog should pop up called “First Law Configuration”
- Select the “Input” tab.
- Reconfigure the following inputs:
- Horizontal (Left stick horizontal axis)
- Vertical (Left stick vertical axis)
- Laser (Right trigger)
- Missile (Left trigger)
- Throttle (Right stick vertical axis)
- Roll (Right stick horizontal axis)
- MatchTargetSpeed (Right stick button, aka R3)
- PreviousTarget (Right Bumper)
- NextTarget (Left Bumper)
- SpawnEnemy (A button)
That should be it! I’m hoping to actively improve this in the future (and support more gamepads).
- Running in a non-native screen resolution on OSX 10.8 seems to have very weird results (cameras go missing on the right eye). So for now pick whatever screen resolution you’re actively using.
- The InputManager stuff on mac os (see the instructions above)
- I lied about what the quit key is. I think it’s actually the Esc key.
Find another issue? Please let me know! You can either leave a comment on this page or send me a note on twitter.