Beyond the Red Line for all you battlestar fans...
#1
Posted 03 April 2007 - 12:18 PM
Enjoy!
#2
Posted 03 April 2007 - 12:57 PM
Macbook Pro - C2D 2.4Ghz / 4Gb RAM / WD Scorpio Black 320GB ( 255GB OSX v 42GB XP ) / Geforce 8600M GT 256Mb / 15.4"
Cube - G4 1.7Ghz 7448 / 1.5Gb RAM / Samsung Spinpoint 250GB / Geforce 6200 256Mb
We won! Apple offer the 17" with a matte screen! Well... at a price...
#3
Posted 03 April 2007 - 01:37 PM
Using the Scylla/Pegasus story is very cool!
Slow torrent, but I'm patient.
I was bummed about the wait until next season, but I just downloaded the podcast commentaries for all my stored eps from iTunes, plus now I have this to tide me over
#6
Posted 04 April 2007 - 08:37 PM
#8
Posted 04 April 2007 - 09:58 PM
In my case, mouse does work in-game, but in the menus it causes a hard freeze--even Force Quitting doesn't work... until 60+ seconds pass and then the app quits and my Mac is back to normal.
Workaround: nudge the mouse VERY carefully to just the TOP of the bottom-edge buttons. This reduces the freezes, but they still happen. It took me a LOOOOONG time to even get the tutorial started, just because the menus were not working.
I don't think this bug happens for everyone, but one other person at Macologist did report the same.
#9
Posted 05 April 2007 - 06:01 AM
I also edited fs2_open.ini (in App Support > Beyond the Red Line) to make the game run at my iMac's native 1920x1200 widescreen. Perfect! Menus are stretched, but 3D view is not. It just fills the screen properly and looks great.
Now that I know to AIM FOR THE OCTAGON, I do OK--at easiest setting--with a mouse! With gamepad stick, it's hopeless. No control--but I'm sure flight sim veterans would do fine.
Only problem is, my mouse at max sensitivity still can't turn fast enough to catch that last Raider by the mining ship. (Stick can, but up close like that the accuracy of the stick is more frustrating than ever.)
#10
Posted 05 April 2007 - 11:25 PM
nagromme, on April 5th 2007, 08:01 AM, said:
Known bug, and it will hopefully be fixed in the next version of FS2_Open.
The freezing issue is on the todo list of things to fix. There also appears to be a graphics problem for people with an ATI x1600 video cards, but hopefully that will be tracked down soon.
#11
Posted 06 April 2007 - 02:01 AM
For that one Raider ("Fractal"), I'll probably try burning far away at top speed, then turn around and try to get in some shots as he comes after me.
#12
Posted 06 April 2007 - 03:30 PM
nagromme, on April 6th 2007, 01:01 AM, said:
I chased that tin butt in circles for 20 minutes the other night when suddenly a little light went off in my head and it occurred to me that just maybe, that's what they put glide mode in for. Of course, I then ran out of ammo
Bif
#13
Posted 06 April 2007 - 11:19 PM
(BTW, a mistake in my .ini tip above: there's a "Beyond the Red Line" folder in ~Library. NOT in App Support.)
#14
Posted 07 April 2007 - 11:38 AM
BifBologna, on April 6th 2007, 05:30 PM, said:
I ran out of ammo, too... but, then I figured that if I could get up enough speed and get a raider to chase me, I could lead him right into an asteroid. I eliminated two toasters that way.
Unfortunately, my Fighterstick, Pro Throttle and Pro Pedals confuse the game's inputs, which leads to some nausea-inducing sommersaults when anything other than the Fighterstick are connected. (I posted this on the BtRL forum.)
NASA Mid-Atlantic SpecE30 driver #59
#15
Posted 07 April 2007 - 02:49 PM
mustang_dvs, on April 7th 2007, 01:38 PM, said:
Yeah, the joystick controls are rather limited in the engine. It's one of the few things that hasn't had a single upgrade since the source code was released 5 years ago. That's going to change later this year though, as I'm redoing it all with support for more joysticks, more POV HATs, and more axes. At that point it should properly handle whatever you throw at it.
But for now there just isn't really anything that can be done to deal with the problem, it's going to take a major code rewrite to fix.
#16
Posted 07 April 2007 - 03:01 PM
#18
Posted 07 April 2007 - 03:48 PM
Try keeping the mouse above the bottom of the screen--don't touch that deadly last 1/2 inch. When you need to click Continue or something at the bottom, INCH THE MOUSE SLOWLY DOWN until the button JUST lights up, and click right on that top edge (sometimes even higher than the button will work). Get in the habit of not clicking bottom-edge buttons carelessly.
This made all the difference for me. Once you're playing, the issue is gone. It's just with the menus. (And they know about it--they're fixing it for a future version.)
Note, if it does freeze in the menus, push the mouse upward and wait maybe 120 seconds--it generally comes back to life.
#19
Posted 08 April 2007 - 03:43 AM
Voice acting resume fired at them post haste. No doubt they're full up by now, but judging by the off-kilter work of the briefing dude, they could use at least one more professional.
Cypher - 4 x G5 2.5 GHz / 6.5GB RAM / WDC 250GB, ST 1.5TB / 7800GTX 512MB / MacOS 10.4.11, 9.2.2
Spike - Cell 3.2 GHz / 256MB RAM / ST 320GB / RSX 256MB / GameOS 3.15, YDLinux 6.2
When there's a multiplayer version, I'm going to be on Frost's team. Well, except he doesn't seem to actually need a team...I mean, what's the point? "Hey look, it's Frost and His Merry Gang of Useless Hangers-On!" Or something.
#20
Posted 08 April 2007 - 02:31 PM
Aside from totally running out of ammo on my first "mission" (exactly how close does one need to be to damage hostiles, it seem to me like I have to be on their tail within 100-150 feet) the one thing that seems problematic is that sometimes when I "launch" a mission, I sit there spinning like crazy. Sometimes it seems perfect, I'm flying pretty much straight and level from the get go.
Anyone having "flaky joystick" like I am? Known issue?

Sign In
Register
Help


MultiQuote




