Patch Notes Update Update 1.1.05 incoming (19.02.15)

Status
Thread Closed: Not open for further replies.
Dunno if this is new buggyness or simply luck that I've not seen it before - 2 issues this evening:

1) several times got a pad loitering warning when I was doing no such thing: enter the station at about 80 and flying down the middle axis, more or less. The infraction cleared immediately, so not a big deal - but it shouldn't happen, I was nowhere near a wrong pad. This is on stations where I've previously docked on multiple occasions with no issues.

2) Much more serious. Interdicted by a NPC, flying my well equipped Asp (D5 shields, plenty of weapons) so thought no biggie, I can either kill it or run away - zeroed the throttle to submit. Except the ship came to a stop from FSD fail with NO POWER. no throttle, no engines, no thrusters, speed zero. Attitude control with the stick worked, but all keyboard bindings for motion, nada. Not surprisingly the cobra that interdicted me proceeded to shoot up my shield, kinda hard to fight in a stationary ship. Luckily, it didn't kill me in the 15 second delay until I could save and quit. Still, 84K credits of damage.

Did the cobra just get fantastically lucky and kill my engines through the shield? I doubt it. The shield is plenty big enough to cover the whole ship. Much more likely it's a bug of some kind. Let's hope it was a one-off or things are going to be "interesting"...
 
... 1) several times got a pad loitering warning when I was doing no such thing: enter the station at about 80 and flying down the middle axis, more or less. The infraction cleared immediately, so not a big deal - but it shouldn't happen, I was nowhere near a wrong pad. This is on stations where I've previously docked on multiple occasions with no issues. ...
That chestnut of a BUG has been around since Beta. Reported forever, never fixed.
 
Dunno if this is new buggyness or simply luck that I've not seen it before - 2 issues this evening:

1) several times got a pad loitering warning when I was doing no such thing: enter the station at about 80 and flying down the middle axis, more or less. The infraction cleared immediately, so not a big deal - but it shouldn't happen, I was nowhere near a wrong pad. This is on stations where I've previously docked on multiple occasions with no issues.

2) Much more serious. Interdicted by a NPC, flying my well equipped Asp (D5 shields, plenty of weapons) so thought no biggie, I can either kill it or run away - zeroed the throttle to submit. Except the ship came to a stop from FSD fail with NO POWER. no throttle, no engines, no thrusters, speed zero. Attitude control with the stick worked, but all keyboard bindings for motion, nada. Not surprisingly the cobra that interdicted me proceeded to shoot up my shield, kinda hard to fight in a stationary ship. Luckily, it didn't kill me in the 15 second delay until I could save and quit. Still, 84K credits of damage.

Did the cobra just get fantastically lucky and kill my engines through the shield? I doubt it. The shield is plenty big enough to cover the whole ship. Much more likely it's a bug of some kind. Let's hope it was a one-off or things are going to be "interesting"...
Did you have the comms panel open? It happens to me sometimes. I realize it after a bunch of seconds in which I cannot move. Basically, if you come out of supercruise while keeping one of the panels key-binding pressed, you automatically enter the panel without the 'double' shortcut combo (e.g. shift+...).
 
My hope is that, eventually, these things would resolve during a maint window. In the future we won't always have updates so often (fingers-crossed).

I presume the first few incarnations will be fingers-to-keyboard, with scripting to follow to handle it more dynamically.
 
My hope is that, eventually, these things would resolve during a maint window. In the future we won't always have updates so often (fingers-crossed).
My hope, both for players and the poor devs responsible for the manual updating right now, is that this eventually just update real-time and be visible as soon as anyone re-gets a copy of that instance.
 
- Station defences beefed up and not confused by chaff


dude... just why?

Are the turrets immune now because the design team decided to add another artificial balancing "rule" or is there a better explanation? Or maybe even a better way for whatever FD tries to archive here?

I fully understand that sometimes things have to be balanced the hard way but I think FD developed the strong tendency of fixing everything with half-cooked ideas and it seems to head in the wrong direction in terms of immersion (and for me immersion kicks in if there is a bit of authenticity, plausability and even believability)

Same goes for the friendly fire system, as I've mentioned in other posts. How awesome would it be if each NPC would actually individually evaluate how to react after being shot at, instead of implementing some static artificial rules that are making the NPCs so predictable and therefor boring.
https://forums.frontier.co.uk/showthread.php?t=110816&highlight=
 
Last edited:
It is technically possible to have dynamic server driven updates to all clients, in real time. This has been possible in all massively multiplayer persistent games since 1996. It was routinely used on the scale of 16-32 clients (E|D scale) since 1993.

FDEV has CHOSEN not to implement this feature that was demonstrated to be possible ~20 years ago. Chosen not to.
I'm not "demanding" anything that hasn't been demonstrated/proven possible for a very long time.
I expect that FDEV would implement modern gameplay elements with proven features and technology. So far? Nope.

Unfortunately...P2P.
 
System LHS 6309 appears to have changed completely since 1.1.0.5
Whole new set of different stations.

I didn't see in the Patch Notes that there were going to be Proc Gen changes to systems ...
Anyone else seen Star System changes since the Patch ?
 
Just docked at the new station 'Under Construction' in system New Yembo ... it orbits the waterworld New Yembo 11.
It consists of the basic station cylinder.
The Top Benefactors are also listed on the info page of the station.
 
Last edited:
If you look at the details for each they are there already before your scan. It seems this might be one of the previously scanned systems that didnt give credit for being scanned, hence the unexplored tag.
If Im correct it wont give credit cause as Michael said previous scanned systems won't. Im guessing neither the orginal scanner nor any new scanner will get credit for systems that even though say unexplored show details for the stars/planets.

2nd thought, I think all systems will show the unexplored tag for you until you visit and scan, this allows us all to sell data not just the first scanned explorer.

Edited for 2nd thought

Concerning the Exploration Discovery Bug

https://www.youtube.com/watch?v=TL1AnL-CXQA
 
Last edited:
Dunno if this is new buggyness or simply luck that I've not seen it before - 2 issues this evening:

1) several times got a pad loitering warning when I was doing no such thing: enter the station at about 80 and flying down the middle axis, more or less. The infraction cleared immediately, so not a big deal - but it shouldn't happen, I was nowhere near a wrong pad. This is on stations where I've previously docked on multiple occasions with no issues.

2) Much more serious. Interdicted by a NPC, flying my well equipped Asp (D5 shields, plenty of weapons) so thought no biggie, I can either kill it or run away - zeroed the throttle to submit. Except the ship came to a stop from FSD fail with NO POWER. no throttle, no engines, no thrusters, speed zero. Attitude control with the stick worked, but all keyboard bindings for motion, nada. Not surprisingly the cobra that interdicted me proceeded to shoot up my shield, kinda hard to fight in a stationary ship. Luckily, it didn't kill me in the 15 second delay until I could save and quit. Still, 84K credits of damage.

Did the cobra just get fantastically lucky and kill my engines through the shield? I doubt it. The shield is plenty big enough to cover the whole ship. Much more likely it's a bug of some kind. Let's hope it was a one-off or things are going to be "interesting"...

Just a thought - how much power drain do you have?
If you have 99% power used, then a small amount of damage to the power plant will cause power use to be >100%. If every module is priority 1, then the first thing to shut down is the thrusters...
I make sure that FSD, dual scoop, docking computer are all 2nd or 3rd priority to allow for minor power loses.
With shield cells taking more power now than they used to, every user should double check their settings.
 
actually, with the number of system planned, and the planned evolution of the game.....damn right this should be automated .

run the number, do you really think the dev should dedicated i don't know how many hours, once or twice a week to add new stations? really?

what about in even ONE year?

sorry but this kind of thing should be automated, there is no way this can be babysat like this, it's just plain dumb waste of resources and lack of vision

What makes you think you're so smart? What makes you think the development team is churning through mountains of spreadsheets before they say "Oh, we should put a station in this system!" What makes you think that you're so ahead of the ball game, that you know exactly what's going on in the FD offices?

What if I told you that, in reality where you have no idea how their systems work, the system tells them on a daily basis what star systems are candidates for having a new station in it? What if I told you that, from that data, they decide to put in the new station, knowing full well that a completely unchecked background simulation could end up with unforeseen consequences that us end users can't understand?

What if I told you that you had no vision yourself?



It's posts like this that make me wonder how anyone at FD can get through a day without exploding on these forums. The attitude from so many people here is so unbelievably toxic, entitled, and pompous it baffles me. The demands and expectations are ludicrous. A patch is released that fixes a number of issues but WHOA BABY THE KILL COUNTER RESETS AFTER I GET A COUNTER-OFFER HOLY CRAP WHERE'S MY REFUND. I have nights playing League of freakin' Legends with less toxicity than is presented on these forums. Perhaps I contribute to this polarization, but, when I read things like above, it gets the blood flowing...
 
Last edited:
Dunno if this is new buggyness or simply luck that I've not seen it before - 2 issues this evening:

1) several times got a pad loitering warning when I was doing no such thing: enter the station at about 80 and flying down the middle axis, more or less. The infraction cleared immediately, so not a big deal - but it shouldn't happen, I was nowhere near a wrong pad. This is on stations where I've previously docked on multiple occasions with no issues.

2) Much more serious. Interdicted by a NPC, flying my well equipped Asp (D5 shields, plenty of weapons) so thought no biggie, I can either kill it or run away - zeroed the throttle to submit. Except the ship came to a stop from FSD fail with NO POWER. no throttle, no engines, no thrusters, speed zero. Attitude control with the stick worked, but all keyboard bindings for motion, nada. Not surprisingly the cobra that interdicted me proceeded to shoot up my shield, kinda hard to fight in a stationary ship. Luckily, it didn't kill me in the 15 second delay until I could save and quit. Still, 84K credits of damage.

Did the cobra just get fantastically lucky and kill my engines through the shield? I doubt it. The shield is plenty big enough to cover the whole ship. Much more likely it's a bug of some kind. Let's hope it was a one-off or things are going to be "interesting"...

I've done similar a couple of times, I'd accidentally hit the comms toggle on the stick and not noticed. Everything stops working other than joystick axis, even the throttle, as it's waiting for you to type in the comms panel. Looked up and saw a random string of characters as I'd been hitting keys right left and centre trying to get a response :)

Edit: Doh, ninja'd
 
Last edited:
I've done similar a couple of times, I'd accidentally hit the comms toggle on the stick and not noticed. Everything stops working other than joystick axis, even the throttle, as it's waiting for you to type in the comms panel. Looked up and saw a random string of characters as I'd been hitting keys right left and centre trying to get a response :)

Edit: Doh, ninja'd

first rule of forums, ain't it?

thanks for the suggestions. I don't have joystick bindings to comms, but I could've hit 2 by mistake, quite easily. I'll watch for that in future.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom