Aren't you guys suppose to say: No worries.
That's what I remember from my trip down below anyway. A breath of fresh air compared to basically being harassed by LA customs when passing through there on our way.![]()
You mean 'No Wucken Forries' ?
Aren't you guys suppose to say: No worries.
That's what I remember from my trip down below anyway. A breath of fresh air compared to basically being harassed by LA customs when passing through there on our way.![]()
We never have and we never will, not with EA, not with Ubi, certainly not with Blizzard. This is why having a "solo" mode that requires a net connection is totally and utterly unacceptable until the availability and stability of servers can be guaranteed. We're over a month from release now, breaking servers with a minor update is little league stuff.
Same error occurred when setting up my brothers account. Had to do with DirectX, not ED
Do you have the single player combat training installed? A friend of mine had this same error until he uninstalled the single player combat training.
Hi Michael, are there any plans to make station news more location aware and graphically memorable? It's difficult to recognize top tier NPC's when it's just names in a text box.
We never have and we never will, not with EA, not with Ubi, certainly not with Blizzard. This is why having a "solo" mode that requires a net connection is totally and utterly unacceptable until the availability and stability of servers can be guaranteed. We're over a month from release now, breaking servers with a minor update is little league stuff.
Hi Michael, I'm getting a validation error when I try and upgrade
c:\users\admin\appdata\local\frontier_developments\products\FORC-FDEV-D1010\WIN32\data.ovx
Any ideas what this is? Thanks
- Fixed issue with influence
Well after 1.06 I still have the unacceptable Federal mission for the Sol permit. I already have a Sol permit from being a Founder. I am ranked Midshipman. I have Sol, Beta Hydri, Plx 695 and Founder world permits after 1.06.
Any fix for this?
There was I thinking it was the electrics on the blink... Just a random hazard of docking. Can't we intentionally have minor outages like this, or even selecting "Enter Hangar" not working due to a mechanical failure so you're assigned a new docking pad (if you're lucky and there's one available), but with a tighter time limit - or the option of accepting a small financial credit from the station or outpost if you leave right away? Subsequent docking requests which would otherwise be denied for a sensible period of time could be denied with a new reason while repairs were undertaken.
Random thoughts...
In Australia can't connect to server!!!!!!!!
In Australia can't connect to server!!!!!!!!
Good news. Heres a video showing the second bug a little more in depth, I'll add it to my ticket as well if its possible.The first is fixed in 1.1. I'm not sure on the second.
Michael
Looking at it doesn't seem to be working. Can you try harsh language?