Starward Rogue BETA 1.502 (Plus upcoming kickstarter expansion!)

[x4000]

Original: http://arcengames.com/starward-rogue-beta-1-502-plus-upcoming-kickstarter-expansion/

New beta build for you!  To get this one, you'll need to right-click the game in Steam and hit Properties, then go to Betas and opt into the beta for this game.  Right now the guys are basically looking for feedback, because this is a huge number of changes!

There's just an incredible, incredible amount of stuff in there.  The biggest single group of changes is in the perk overhaul, though; that's a really exciting one.

Expansion Kickstarter?

Yep!  Details on this are scarce right now, but basically the volunteers behind all these awesome free updates over the last year are putting together a paid expansion pack with even more new features.  We'll have more on that coming up, and a link to the kickstarter and all that when it's going live, of course.  For now I just wanted to mention that that's a thing on the horizon!

It's completely separate from anything Keith and I are doing on the AI War 2 kickstarter, as an aside.  So no worries about negative overlap there in either direction.

[Pepisolo]

Yeah, guys, we could do with testers for this to check out all the new changes. Save games should still work, but you might want to back those up just in case. The new perk icons are not yet final, although feedback on which ones look fine and which don't might be useful. The icons were created using repurposed art without Blue's expertise, so there might be a few dodgy ones. Blue will be taking a look nearer the proper Steam release.

There are fixes in place for that dreaded R6025 virtual crash thingy, so hopefully that problem is fixed, but maybe not as it's been pretty tricky to pin down why that crash happens. We're mostly just looking for general feedback, difficulty feedback etc. Whatever you've got. Cheers!

[ElOhTeeBee]

Probably not the best time to announce a kickstarter, regardless of whether or not anyone on AI War 2 would be working on it.

[x4000]

Probably not the best time to announce a kickstarter, regardless of whether or not anyone on AI War 2 would be working on it.

It's absolutely the time to announce it -- waiting until after the fact to mention it is much much worse.  Given we have full intent of this (though it won't even be under Arcen's account on kickstarter -- this is separate folks working on it, etc), it's much better if we let people have all the information now.

I imagine that your argument is probably that people may avoid backing one of them for fear we're doing something shady?  There might be other reasons, but that's my top one, anyway.  In those cases, I'd rather have people not back us based on having info in advance instead of back us and find out an unpleasant (to them) surprise.

I've talked about this a fair bit on the later updates of the first AI War 2 kickstarter -- and while I'm not intending to make it some sort of in-your-face "look at this other thing!" issue, I do want to be clear in terms of "hey, full disclosure, here's what's up and why it's not what some other dirtbag developers have done."

That's the rationale, anyway. 

[x4000]

There are fixes in place for that dreaded R6025 virtual crash thingy, so hopefully that problem is fixed, but maybe not as it's been pretty tricky to pin down why that crash happens.

Ooh, I didn't hear about that fix.  What was it, in the end?

[Pepisolo]

There are fixes in place for that dreaded R6025 virtual crash thingy, so hopefully that problem is fixed, but maybe not as it's been pretty tricky to pin down why that crash happens.

Ooh, I didn't hear about that fix.  What was it, in the end?

Actually, I was referring to that fix you put in way back. Something to do with enabling virtualization at all times rather than switching it on or off......? Something like that. I'm hoping that fixed it. So, yeah, that thing that you put in which you might've forgotton about, heh.

[x4000]

OH.  Right, I totally forgot about that.  Wow, back in September.  Derp!

[ptarth]

Chris did it. Might have just been the impact of using updated version of Unity.

[x4000]

Chris did it. Might have just been the impact of using updated version of Unity.

No, this was further back.  What I did:

I made it so that it now always keeps the brightness/contrast shader active at all times, versus turning it on and off between those rooms.  The virtual method call issues can happen when certain things are disabled, so that might have been the issue.

[Logorouge]

That potential fix for the virtual crash will be most welcome. Not knowing when the game might crash was pretty nerve racking. :P
It will be exciting to be able to test out the game with all those fixes and additions.

[Misery]

Ah, so this is ready, then.

Here's hoping nothing bursts into flames.

Unless it's supposed to.

[Logorouge]

Ah, so this is ready, then.

Here's hoping nothing bursts into flames.

Unless it's supposed to.

For what it's worth, my existing save ran without any issue but my mech ended up bursting into said flames as I died...on Normal. Gotta pay more attention now that I can't just steamroll everything. :)

[Misery]

For what it's worth, my existing save ran without any issue but my mech ended up bursting into said flames as I died...on Normal. Gotta pay more attention now that I can't just steamroll everything.

[Logorouge]

Sorry to be the bringer of bad news:



On the fifth floor, while teleporting rapidly from room to room with the Blue mech.
Attached are all the files I thought could be relevant. I'll wait to run the game, in case I forgot something.

[Pepisolo]

Sorry to be the bringer of bad news:



On the fifth floor, while teleporting rapidly from room to room with the Blue mech.
Attached are all the files I thought could be relevant. I'll wait to run the game, in case I forgot something.

Drat! I feared that we hadn't fully dealt with the problem. Unfortunately, I'm not sure there's anything more we can do about this. It seems to be way too deep in the engine (or Unity) for us to be able to fix.