Patch Notes Update Gamma 2.02 Incoming

Status
Thread Closed: Not open for further replies.
Using target just fine here (Warthog Hotas) - if you use lots of keybinds in your target profile and happen to have a non UK/US keyboard, chances are beta 2 messed up your custom binds file - I had to rebind a lot after beta 2. The issue should have been fixed as of beta 2.1, but by then I had rebound everything already.
 
Bump! AMD Radeon 7900 series and OSSOD (orange spinning ship of doom). Done a full re-install, changed graphics settings, saved and exited but still the orange ship sticks. (in Solo or open). No been able to get into the game since the initial Gamma v2.

However, slightly interestingly, when I do a <CTRL> <ALT> <DEL> to open he task manager and then <ALT> <TAB> to the task manager I am able to see the graphics settings menu. Nothing is selectable so I just force close the application.

Glad this is Gamma testing and NOT the live Game code. Just hope V2.03 fixes it!
 
Personally, I think restricting the supply is the wrong way

What they should do is vary the balance strategy depending on the rare and its location. OK one method is to reduce the profit per distance for freely available rares so big haulers do not make ridiculous sums. Another method for different types of rare would be to restrict supply per player, so a player only sees a few units per day by a trick of instancing or the supplier carries more visible stock but imposes a units per commander restriction due to the special nature of the commodity, which would be enough units to give a nice boost for small and intermediate cargo carriers but not over the top for big haulers.

BTW can anyone tell me if a special/rare commodity listing shows up in the commodities market manifest if there is zero stock?
 

Deleted member 38366

D
Oh well, so Gamma 2.03 will have to do the Trick I guess (and hope). The rotating ship Soft-freeze has been with me (AMD R9 290 GPU) since Gamma 2.00 as well...
 
Last edited by a moderator:
locked spinning ship issue - fixed by first going into game options Graphics, change to full screen. then Play Solo and game loaded then ESC and Options Graphics to set it back the way I like.

Weird but that did fix it for me after a day of OSOD.
 
Using target just fine here (Warthog Hotas) - if you use lots of keybinds in your target profile and happen to have a non UK/US keyboard, chances are beta 2 messed up your custom binds file - I had to rebind a lot after beta 2. The issue should have been fixed as of beta 2.1, but by then I had rebound everything already.

Glad you don't have the same problems as me. I have a UK keyboard. Do you still get the dropdown box for Custom or are you using Generic Joystick as the base profile? I start with Warthog and modify it, so it becomes custom. I then run my target stuff on top of the Custom profile ... are you doing anything different?
 
I am afraid, I didn't read through all of the gamma 2.x threads, so maybe this was mentioned already:

In the galaxy map (which performs WAY better now!), Alliance and Empire colors are now nearly indistinguishable close together (both red). The yellow of the previous iterations was fine. Why change it? Or is it a bug?
 
Glad you don't have the same problems as me. I have a UK keyboard. Do you still get the dropdown box for Custom or are you using Generic Joystick as the base profile? I start with Warthog and modify it, so it becomes custom. I then run my target stuff on top of the Custom profile ... are you doing anything different?

Probably mostly different. I have rebound most buttons to combined keypresses (long story), then just set up a custom profile in ED. It never changed from custom for me - a lot of my bindings were faulty or gone after upgrading to beta 2 though. I've read that there was a problem with key binds on non UK/US keyboards in the patchnotes for beta 2.1. Since I use a german layout, I assumed that was the underlying issue.


Target as such doesn't seem to be a problem - I only use very basic scripts though (making the second stage of the trigger firing all guns, auto-firing a heatsink when enabling silent running... that kind of stuff). What scripts do you use?
 
Last edited:
damn I haven't had a bad play experience since beta began, now since gamma 2.02 I can't do anything. Gamma 2.0 was fine, now since they tried to fix the ship spinning bug, I've caught the ship spinning bug, constant disconnects....man I wonder if MY save or character is corrupt......maybe now they should wipe :)
 
Same here...WHY IS NO ONE OF FRONTIER give an explanation of what the issue is..Darn.so we know .This just sucks.I know its gonna be fixed.Was update 2.0 such a big update,or what?If it was the made huge differences i suppose..Well,maybe 2.03 or 2.040506070809 will fix it..:-S
 
[h=1]Viewing Ticket [ id: 59827 ][/h][h=2]Crash to desktop consumes fuel[/h]Thu 11th Dec 2014 23:35



With the release of gamma 2.02 there have been several issues with servers after the update.
Warping to new system is causing crashes to desktop.
I retried 3 times in 15 minute intervals.

On last try for the night I noticed I ad no fuel.
It seems that each crash on warp it still subtracts fuel although you restart at system where jump started from.

I did mange to limp to sun and refuel

Although I crashed on jump again .... done for the night.

Not a big bug but can be an issue if you cant refuel.
 
Just played over 2.5 hours on 2.02 without issue running Solo, only gripe still not found these Military Plans I am hunting for,
made 45,000 with loads of Trade Data I picked up from Derelicts at USS locations though.
 
Failed to communicate with server

Cannot do missions

I had this problem several times today, it always worked, when I quit the game to the main menu and started it again, I could continue were I left off and was able to do the mission.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom