Patch Notes Update Beta 2.02 incoming

[GraXXoR]

When you release a patch for a patch that patches a patch, isnt that supposed to fix things, not make them worse?

Congrats on making a crap first impression to new fans and backers! :S

At least Star Citizen has something working.

Saying stuff like that has no positive effect on either this game or your credibility.

BTW. The new Star Citizen 0.9.2 patch has damaged far more than it has fixed.

300i flies like a tired brick. Keybinding to HOTAS is now WORSE than when they had no keybinding at all.. (Seriously, how DID they do that?)

And Mouse is oh so very powerful at dogfighting vs any other control device. Even more powerful than TrackIR aiming and $300 joystick.

So, yes, while technically you CAN play it, it aint much fun since their last patch.

That's why I cam here, only to find the Black SOD!

 

[undercovergeek]

Last login before bed here, played for about an hour shooting the wanted npc's in the resource area, a couple of jumps to hand in messenger missions. Had one logout that let me reload fine.
Making lots of progress in the right direction for me. Loving the ship wear and tear appearance too

For everyone eventually getting on and playing, is this solo or online?

 

[xxThe_Dice_manxx]

Can load up and play training missions, get "cannot connect to server" when trying to play solo or online.

Found a new one where game freezes for several seconds in the training missions, anything from 1 second to 25.

 

[ktulu1975]

yeah - I get an "unconnected" message at the bottom left, with Start redded out. The menu screen is dead anyway - mouse/joystick hat won't move cursor/selections on it. Have to kill process to exit.

 

[regdc]

Thank you very much for all your work in getting Beta 2 and its patches out.

That said, with Beta 2.02 I seem to have gone backwards

I did manage to get into Beta 2.01 to do the Tutorials and get the System Map and Galaxy Map up in Group Mode (with a Group of one, me) and it looked great.

In Beta 2.02, I cannot do anything The Mouse is frozen and the Online Mode is Red and the Server is not connected.

Sob

From what I have seen before, it looks great, but right now I am completely stuffed!!

I have raised tickets.

 

[John_Hudson]

if youve only just started - what are you doing in Dahan?

I managed to get one jump in 2.01 before giving up... I guess there was no reset between 2.01 and 2.02... hence I've started in Dahan... were I left it

solo mode seems to work though

 

[Zenicetus]

I don't know how useful it is to keep posting when it's not working, and it's 2am in the UK so the FD folk should be getting some sleep. But for what it's worth, I still get locked up at the main menu with a red Start button, and the Server info at the lower left of the screen saying "[unconnected]"

It's also still writing a humongous netLog.log file if I let it run more than a minute or two.

 

[[LG] Khan]

Why would you ever reset your MTU off of 1500?:S One of the first things I learned setting up networks. You can Play with anything except the black hole (MTU). So I am really curious why that was not 1500.

Someone suggested it and it worked for me

 

[ShadowGar]

I don't know how useful it is to keep posting when it's not working, and it's 2am in the UK so the FD folk should be getting some sleep. But for what it's worth, I still get locked up at the main menu with a red Start button, and the Server info at the lower left of the screen saying "[unconnected]"

It's also still writing a humongous netLog.log file if I let it run more than a minute or two.

That is very odd. See, I connect to the servers fine. It's just when I click solo/open it then says I was disconnected but still shows connected at bottom.

This is all I get in my netlog......

14-10-01-21:31 Eastern Daylight Time  (01:31 GMT)
{21:31:05} Start Log for this machine: 192.168.2.13:62914 - Shadow-PC
{21:31:28} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e3232382e38372e313538</ip><port>19364</port></server></servers><rescueservers/></data>

{21:31:28} New Primary Server: 54.228.87.158:19364
{21:31:29} Now using address [Redacted]:62914 for this machine after STUN reply
{21:31:29} Established MTU=1500
{21:31:48} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e3232382e38372e313538</ip><port>19364</port></server></servers><rescueservers/></data>

{21:31:48} EnterLocation: Using UDP server address 54.228.87.158:19364 from webserver
{21:31:48} System:2(Morgor) Body:2 Pos:(-1632.13,-1732.47,-1826.11) 
{21:31:48} System:2(Morgor) Body:2 Pos:(-1632.13,-1732.47,-1826.11)

So from what I can see, it is connecting and it is seeing my location in the proper system. It's just not loading me past the spinning ship.

But that server IP of 35342e3232382e38372e313538 ? I'm curious why they don't just use standard ipv4.

 

[xxThe_Dice_manxx]

Does anyone else find it extremely odd that some people are able to play while most can't?

Anyone have any idea's why that might be?

 

[CMDR Crustatious Cornelius Pig]

<removed>

FD has earned my patience over the last year. They will get this figured out and everyone will be back to playing. I do understand frustration in waiting though however with that said dissenting opinions and responses should try to remain civil

 

[flexy123]

Same here.

If it is down to router configuration, well I knew I should have thrown out the BT home hub and got a decent router...

I have never seen an online game, or whatever game whatsoever which would a) require to tweak MTU that it even works b) get a "special" router or c) need some very "special" router configuration so it works (MINUS in the very old times, before upnp where some games required opening ports on the router)

All that MTU tweaking talk is pointless. I haven't even played 2.0x yet (reading all those replies)..it's a netcode problem...not something YOU or me would need to fix by tweaking MTU or router settings or similar. (And yes, MTU can vary depending on your OS, ISP, type of internet, router etc., this shouldn't and cannot play a role)

 

[ShadowGar]

Does anyone else find it extremely odd that some people are able to play while most can't?

Anyone have any idea's why that might be?

Well the question that hasnt been asked is...

The people that can connect...
1.Where do they live?
2.What does it show in their netlog when they do connect?

Doing trace's back to a couple server IP's are showing me connecting to Dublin Ireland. Which explains the horrible amount of lag I get since I'm on the eastern seaboard of the US.

I'm betting that the people that are connecting without any problems are closer to the server and possibly running the same ISP settings as that they are closer to that server.

State side ISP's run way different settings than over the pond.

 

[Wakner]

Someone suggested it and it worked for me

Changing MTU to 1500 (in OS, not router) seemed to work for me too : previously wasn't able to connect at all as has spinning ship and main menu screen hangs Al the time.

Changed MTU from 1300 to 1500 and had a couple of hours of crash free play in 'solo' mode (didn't try 'open').

It could, of course, have been pure coincidence with Frontier making some sort of server change at the moment I made my MTU change - judge for yourselves.z

Cheers

Ads

 

[CMDR Crustatious Cornelius Pig]

I have never seen an online game, or whatever game whatsoever which would a) require to tweak MTU that it even works b) get a "special" router or c) need some very "special" router configuration so it works (MINUS in the very old times, before upnp where some games required opening ports on the router)

All that MTU tweaking talk is pointless. I haven't even played 2.0x yet (reading all those replies)..it's a netcode problem...not something YOU or me would need to fix by tweaking MTU or router settings or similar. (And yes, MTU can vary depending on your OS, ISP, type of internet, router etc., this shouldn't and cannot play a role)

it is a netcode issue. Don't play with your MTU settings. The issue is a defect or multiple defects in 2.02....they will fix it. give them some time

 

[Zenicetus]

All that MTU tweaking talk is pointless.

Agreed, I'm not messing with my router. This game worked fine for me in Beta 1, very smooth in Solo Online at least, although glitchy in All Online as should be expected with a Beta. I'm going to assume that what worked on my computer and network setup in Beta 1, should work in Beta 2 once they get this sorted.

 

[CMDR Bogfisg]

Why some people can play and most can't

It all seems to come down to MTU
my network provider will fragment packets over 1450 bytes it will send packets of 1442 bytes and under reliably packets between 1442 bytes and 1450 bytes sometimes work and sometimes fail.
From my packet sniffer I can see some very big packets coming out of Elite (some nearly 1500 bytes) and indeed the log confirms that elite believes that the MTU is 1500 (interestingly even if you change the windows MTU to something lower!)
If i change my MTU to 1442 the game will hang on the main menu and generate a huge netlog.log file
I suspect that the people for who things are working do not traverse any networks with 'black holes' these are network connections that don't handle packets between 1440 bytes and 1500.
I suspect if Frontier changes it's maximum network buffer size to say 1024 bytes suddenly all will work OK
and before you ask yes I have put all this in a bug report but I doubt it will be read among the thousands of others

 

[ktulu1975]

Well the question that hasnt been asked is...

The people that can connect...
1.Where do they live?
2.What does it show in their netlog when they do connect?

Doing trace's back to a couple server IP's are showing me connecting to Dublin Ireland. Which explains the horrible amount of lag I get since I'm on the eastern seaboard of the US.

I'm betting that the people that are connecting without any problems are closer to the server and possibly running the same ISP settings as that they are closer to that server.

State side ISP's run way different settings than over the pond.

well I'm in Northern Ireland (relatively close to Dublin) although I'm getting the [unconnected] message bottom left and frozen menu screen... ...

 

[Zenicetus]

Doing trace's back to a couple server IP's are showing me connecting to Dublin Ireland. Which explains the horrible amount of lag I get since I'm on the eastern seaboard of the US.

I'm betting that the people that are connecting without any problems are closer to the server and possibly running the same ISP settings as that they are closer to that server.

State side ISP's run way different settings than over the pond.

I dunno... I read here on the forums somewhere that they're using leased Amazon AWS Cloud servers for the matchmakers/data download feeds. Don't know how accurate that is. If they are, then that's distributed geographically in several different worldwide regions, according to the AWS web site.

I'm betting it's a netcode issue specific to some user's local computer settings and not others, instead of server location or just servers getting hammered with a new Beta release. I've had the same problems trying to log in, during what should be a fairly quiet time for server traffic. They changed something that worked fine (at least in Solo Online) in Beta 1.

 

[xxThe_Dice_manxx]

well I'm in Northern Ireland (pretty close to Dublin) although I'm getting the [unconnected] message bottom left and frozen menu screen... ...

Same, Belfast here, we should be having no problems at all.

Which leads me to my theory that the devs are restricting access.