Patch Notes Update Beta 2.06 incoming

Status
Thread Closed: Not open for further replies.
Still at spinning ship v2.06

Haven't been able to get past spinning ship since 2.04. Clearing the save has no effect.

Netlog reports .....

{09:59:08} EnterLocation: Using UDP server address 54.73.193.222:19364 from webserver
{09:59:08} New Primary Server: 54.73.193.222:19364
{09:59:10} ModularStationAttachComponent: object kinematic Civ_FuelTanks_0x0000000100000010 is not ready
{09:59:10} ModularStationAttachComponent: object kinematic Civ_FuelTanks_0x0000000100000010 is not ready
{09:59:12} Established MTU=1244
{09:59:16} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:16} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:17} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:17} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:18} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:18} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:18} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:19} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:19} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:20} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:20} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:20} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:21} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:21} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:21} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
{09:59:22} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1
 
Last edited:
Hi all,

Glad that most of you seem to be getting by in the game. For those still experiencing issues, please log your tickets/crash reports so the team can continue working through them.

Feedback, both good and bad, is welcomed.
 
Also..

The heat sink launcher claims to only have 3 ammo slots, but it gets refilled to 4, and does in fact launch four. It does 3/3 first, then switches to 1/1, then finally is empty.

When you buy it, initially, it only has 3, then you refill it, it has four, and from that point forward always will have four as a max capacity.

Doesn't really make a lot of sense, though? :S

As well, although this may just be me, I've never seen an upgrade to the heat sink launcher, nor the ability to mount more than one.. Not sure if that's intentional or not.

This is probably why the Beta 2 version always seamed to be leaking coolant, some one has a variable set differently log in you get 3 load the extra one, you have 4, log out log in oh you have 3....Thought it was the faulty plumbing
 
no fix for:

  • not being able to target enemies
  • incorrect bounty placement
  • fed's unwarranted attacks
  • not being able to choose a faction.

grrrr. guess I'll keep waiting to be able to play with my friends

You mean, "test with my friends". :)


Someone at ED needs to run the game with this BUG happening 24/7, its unplayable, its like playing Descent in the 90s, I dont think anyone experiencing this could stand testing the game for too long, I certainly cant...

Haha, Ben Parry, FD's graphic designer, said the other day,

If it's any consolation I'm doing penance, I have to use a 560Ti until it's fixed.

:)

I have this bug 24/7. It's obviously not unplayable for me, as I've been doing all sorts of interesting stuff in this beta. It's a shame you can't stand it, as there's a heap of content once you look beyond the primitive render look.
 
Have you logged the details of your problem?

re: Cannot get past spinning ship.

Yes. Thanks Edward. I raised a ticket for 2.05 and 2.06 for the same issue.

Last support reply suggested clearing the save, but this had no effect. Netlog suggests that the server cannot allocate resources.


{09:59:26} Server resource allocation failed, group:0000000007ab3c08 subgroup:DockingBays requested:1

.
 
Last edited:
You mean, "test with my friends". :)




Haha, Ben Parry, FD's graphic designer, said the other day,



:)

I have this bug 24/7. It's obviously not unplayable for me, as I've been doing all sorts of interesting stuff in this beta. It's a shame you can't stand it, as there's a heap of content once you look beyond the primitive render look.

I'm already paying to test the game, and I'm happy with that, but I need to enjoy the process, awful visuals is not my idea of enjoyment, sorry.

And what I don't quite understand about Ben Parry's post is, in that same thread almost one week ago, Ben stated that there is a fix, and its solid...so why hold it back? is not affecting enough people?, its not a priority? instead we get nothing... that's getting frustrating to say the least...
 
Last edited:
I'm already paying to test the game, and I'm happy with that, but I need to enjoy the process, awful visuals is not my idea of enjoyment, sorry.

And what I don't quite understand about Ben Parry's post is, in that same thread almost one week ago, Ben stated that there is a fix, and its solid...so why hold it back? is not affecting enough people?, its not a priority? instead we get nothing... that's getting frustrating to say the least...

Because dev priorities are different at this point. They want to get networking working with isolated patches. Problem is when you have to cherry pick you have to take some resources from developing Beta 3. Be patient. It's not done specially, it is just order of things.
 
Have you logged the details of your problem?

Since the server update of 10.10 with my rift dk2 connected and used as main display, the game (open or solo play) will not load. I get a brief display of sidewinder then just a system hang, I can play the tutorials fine, I have cleared my save endlessly, I cannot get past this issue, I have logged a ticket 5 days ago, still no response.

Prior to the server update The game was functioning perfectly for me on my rift dk2.

I can play normal screen fine, it just appears to be when the rift is the display monitor that it hangs on open/solo play load.
 
still some issues

hey guys, thanks for all the hard work :) but i have bin having the same issue since beta 2 :( if i try to jump to an other system after having taken a "mission" in station..... i get an infinite warp :( on top of that... EVERY station services window is STILL TOO BIG for my screen :p the far left and right edges are extending beyond my frame of view, effectively stopping me from accessing many of the menu options :( i HAVE posted in bugs... but apparently it hasn't bin worked out yet. I would just like to know if anyone has looked into this issue, and if so, are there plans to work it out during the BETA process shortly :) thanks again for your time, and dedication to bring us THE BEST space sim to come from anyone in a very long time ! :D
 
I'm already paying to test the game, and I'm happy with that, but I need to enjoy the process, awful visuals is not my idea of enjoyment, sorry.

And what I don't quite understand about Ben Parry's post is, in that same thread almost one week ago, Ben stated that there is a fix, and its solid...so why hold it back? is not affecting enough people?, its not a priority? instead we get nothing... that's getting frustrating to say the least...

FD isn't holding the fix back.

The whole "version" we're playing now is a development dead-end. It's an offshoot, split from the main project and called "Beta 2".

After splitting it off on a Tuesday, the devs coming in on Wednesday get to work on the main project, which evolves and develops as it heads towards completion.

Well, the devs will TRY to work on the main project. If they get grabbed and directed to address issues in the offshoot "Beta 2", they are shoring up the dead-end Beta 2 release... for whatever short-term benefit that delivers. At that point, their man-day efforts are only contributing indirectly to the overall success of the project, eg.

  • By leading to a greater quantity of bug reports from us, thanks to improved up-time. FD probably isn't lacking from tickets right now. :)
  • By digging past Bug A that is masking Bug B, that could be masking Bug C... and doing that NOW, as opposed to waiting for Beta 3.
  • Getting a newly added feature (like UNIVERSAL CARTOGRAPHY) working and verified, because subsequent dev/scaling work depends on putting that new feature under load.
etc.

If there isn't a hard and fast reason to divert development into the evolutionary dead-end that is "Beta 2", FD aren't likely to do it.

Not with an announced deadline in their sights for "Beta 3".


So apologies to those who have to sell each system map, one by one. FD may not prioritise SELL ALL over and above Beta 3 development. Ditto for the graphics render fix, bounty problems, system authority ship bugs, etc.
 
Last edited:
Dudes. thank you.
All Unknown stellar objects are now coming back as resolved. Massive improvement for an Explorer in solo.

I have always appreciated it when you make these updates, yes you can't fix everyone's "priorities" but hopefully those unsatisfied will be pacified in future fixes based on priorities (yours not theirs).

Keep up the amazing work and dedication.

I will always appreciate it, even if you don't fix that 1 in a million issue in beta that does not stop game play.
 
So apologies to those who have to sell each system map, one by one. FD may not prioritise SELL ALL over and above Beta 3 development. Ditto for the graphics render fix, bounty problems, system authority ship bugs, etc.

I think the graphics bug is in a different category, and not just because I'm getting tired of looking at it. :)

It's a marketing issue. The bug has been there for 2 weeks now, and if the fix isn't rolled in until Beta 3, that's a month where people will be posting YouTube videos and screenshots that make the game look... well, not exactly great.

Maybe FD doesn't have a traditional marketing department, and that might actually be a good thing. But if they did, I can't imagine the marketing department not pushing to fix this particular bug, before too many prospective buyers form a negative impression based on the visuals. Because people tend to do that. The visuals have been very impressive until this bug hit.
 
Last edited:
Seems that some of the graphics issues have been resolved, but not all.

More optimizaton.

Glad to hear the graphics designer has been reduced to using a 560Ti until fixed. Although a better punishment would have been the recommended minimum video card, I'm glad to hear he is now using the card I use. Still a good card, but getting long in the tooth. Yeah! I did not see a marshmallow asteroid this first outing since this patch.

All joking, and ribbing aside..... good work.
 
With the possible exception of the 3rd item on the list I have absolutely no idea what any of the fixes in 2.06 mean. Might has well have written "stuff". I think this "stuff" is meant to improve performance - that's my take on it anyway. Jesting aside - a bit more of a layman's non-technical explanation of fixes moving would certainly be appreciated.

Thanks for all the hard work!
 
With the possible exception of the 3rd item on the list I have absolutely no idea what any of the fixes in 2.06 mean. Might has well have written "stuff". I think this "stuff" is meant to improve performance - that's my take on it anyway. Jesting aside - a bit more of a layman's non-technical explanation of fixes moving would certainly be appreciated.

Thanks for all the hard work!

lol, agreed
 
I do. Still... it's a bit hard to understand that they have a fix ready and simply decide not to include it in two updates since the solution has been found. In the meantime the holo displays (a cosmetic non-issue in my eyes) were fixed with the first update. Why did that not take away precious fixing time for more serious issues?

Agreed. I think FD need to smarten their act regarding what should be a priority bug fix and what isn't.

The gfx lighting bug should have been fixed a lot sooner.
The stuck on spinning Sidewinder bug should have been fixed a lot sooner.

These are game breaking bugs which should have priority, yet a lot of people still suffer from them. So I don't follow the logic behind the person who decides when a bug should be fixed in what update. So if there is some magical game designer logic, then please share, otherwise this has been very sloppy work on FDs part.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom