Patch Notes Update Wings Update 1.2.04 Incoming

Status
Thread Closed: Not open for further replies.
i just went there to buy myself a vulture with the 10% discount and was sour that i couldn't claim the reward, I told myself i wouldn't play until it was fixed.
20 mins later i was in game outfitting a vulture!! How i love this game :)
 
Could you post as well the size of the update please?
Useful to those with small bandwith... I never know if I can just wait in front of my PC or if I need to grab a beer.

So I always grab a beer... just in case.
 
Any fixes for the stuck in hyper space issues?

Make sure you haven't accidentally opened the comms panel (or quick comms). Did that back in version 1.0something and sat in hyperspace for 3 minutes before solving it with the escape key (I think...might have been Return key).
 
In a minor update released before the end of the week we’ll reduce the price of non-trade ships ....

That was from a post from Michael earlier in the week but not seen it happen? Or have I missed something?
 
In a minor update released before the end of the week we’ll reduce the price of non-trade ships ....

That was from a post from Michael earlier in the week but not seen it happen? Or have I missed something?
Already happened, I think in 1.2.03. Vulture, Fer-de-Lance and Dropship got their prices reduced.

Not sure about the Dropship but Vulture went down from about 20 million to 5 million and Fer-de-Lance from 100 million to 50 million.
 
Last edited:
Not a mention about the most obvious and widespread bug to do with system map.

I'm normally quite optimistic, but a patch everyday for 4 days in a row says that you're not getting enough testing in the first place.
I'd suggest running beta for 2 weeks before each major update to get a better representation of scenarios that could cause issues.

I had this exact same thought. To me it seems like they put something to beta for the beta guys to say "looks nice" Then the release it to us Retail players for testing of bugs!
I thought beta was ment to be bug fix/finders? I guess I got it the wrong way round.
 

Deleted member 37733

D
I don't think beta testing is some kind of privilege. It's just mind boggling how the entertainment industry has made an entire generation of people accept broken stuff by default.

By all means, some people think playing games in a beta-state is edgy and stuff, but seriously, I just need a game to work when I have time off to play.
If the game needs serious beta testing, revert to 1.1.06 and put 1.2 in a separate nightly-build or something for the people with special interests. Then release 1.2.xxx when it's stable. Then rinse and repeat for 1.2.3 or 1.3 or whichever was rumored to come before this weekend. (PowerPlay)

inb4 why don't you stop playing the game if you know it broken...

Software is hugely more complex now, bugs are inevitable. WinNT 3.1 had 5 million lines of code, just ten years later Windows Server 2003 had 50 million. If you want to play games from the 1980's then they will probably be largely bug free, but if you want to play a much more advanced modern game bugs are going to creep in.

It's a standard development process to freeze new features at some point and work towards a release date. Bugs cannot be completely eliminated before release otherwise the software will never see the light of day. There is no substitute for testing by thousands of people. It becomes a problem when the developer no longer releases further updates and FD has shown a lot of commitment to continuing progress with ED. None of the bugs I have seen people complaining about are game breaking.

Where you could argue your point is whether FD should have a slower development cycle. But for every person that wants things to slow down there will be at least one other that wants a release as soon as possible. I fall into the latter camp.

Human nature is that people are just never happy and like a whinge.
 
Software is hugely more complex now, bugs are inevitable. WinNT 3.1 had 5 million lines of code, just ten years later Windows Server 2003 had 50 million. If you want to play games from the 1980's then they will probably be largely bug free, but if you want to play a much more advanced modern game bugs are going to creep in.

It's a standard development process to freeze new features at some point and work towards a release date. Bugs cannot be completely eliminated before release otherwise the software will never see the light of day. There is no substitute for testing by thousands of people. It becomes a problem when the developer no longer releases further updates and FD has shown a lot of commitment to continuing progress with ED. None of the bugs I have seen people complaining about are game breaking.

Where you could argue your point is whether FD should have a slower development cycle. But for every person that wants things to slow down there will be at least one other that wants a release as soon as possible. I fall into the latter camp.

Human nature is that people are just never happy and like a whinge.

Well said + 1 rep for you.
 
Software is hugely more complex now, bugs are inevitable. WinNT 3.1 had 5 million lines of code, just ten years later Windows Server 2003 had 50 million. If you want to play games from the 1980's then they will probably be largely bug free, but if you want to play a much more advanced modern game bugs are going to creep in.

It's a standard development process to freeze new features at some point and work towards a release date. Bugs cannot be completely eliminated before release otherwise the software will never see the light of day. There is no substitute for testing by thousands of people. It becomes a problem when the developer no longer releases further updates and FD has shown a lot of commitment to continuing progress with ED. None of the bugs I have seen people complaining about are game breaking.

Where you could argue your point is whether FD should have a slower development cycle. But for every person that wants things to slow down there will be at least one other that wants a release as soon as possible. I fall into the latter camp.

Human nature is that people are just never happy and like a whinge.

Guess you're not a software developer or you develop for entertainment business.
 
Last edited:
Guess you're not a software developer or you develop for entertainment business.

I'd love an example of a piece of modern software that has NEVER had to be patched/updated.

That is, if that is what you were alluding to, if not, I'll grab my coat...

Me? I'd rather have FD's proactive approach to fixing bugs!
 
Could we have a patch to reduce the amount of patches required please.

Because I'm sick of turning the PC on and waiting for yet another update... we don't all have hours to set aside when we can play (the game we paid for).

Thanks.
 
+1 rep. I get an hour off a night while Mrs Bill is watching soaps, so this just chews into my enjoyment of the game.

What I do is watch out for updates on the forum then go turn on the PC, set it to updating then go back to what I needed to do, be it sitting next to the wife or doing the washing up.
When I get chance to play the game is then ready.
 
I'd love an example of a piece of modern software that has NEVER had to be patched/updated.

That is, if that is what you were alluding to, if not, I'll grab my coat...

Me? I'd rather have FD's proactive approach to fixing bugs!

You see trees, not the forest. You thing that what FD is doing is fine because, as you wrote, you want FAST fixing.

Software developing is not just coding, fix bugs, coding, fix bugs. What I see in FD is a lack of IT project management. It's not "what" they are doing ( is fine to fix bugs ) it's "how" is done ( cycles too short, no proper testing )

ED project is too big to be handled like a small software. It's not my opinion, are just FACTS. How many "hot fixes" after patches? and how many patches in 2 months? They need to sit down and plan better for future patches/expansions.
 
Last edited:
You see trees, not the forest. You thing that what FD is doing is fine because, as you wrote, you want FAST fixing.

Software developing is not just coding, fix bugs, coding, fix bugs. What I see in FD is a lack of IT project management. It's not "what" they are doing ( is fine to fix bugs ) it's "how" is done ( cycles too short, no proper testing )

ED project is too big to be handled like a small software. It's not my opinion, are just FACTS. How many "hot fixes" after patches? and how many patches in 2 months? They need to sit down and plan better for future patches/expansions.

Yep... They need to implement an Agile Process, if they don't have one already. If they do.. its broken. All parts need to be brought into a room and start talking, especially Dev/QA. QA should be part of the beginning of the cycle... not brought in as an after thought.. and based off frontiers past track record I suspect there's been very limited QA involvement.. At this point, I honestly think Frontiers software development moto is .. Heck let the users test it, when they report it, we will fix it..:) But I applaud the developers, they pump out the code...and I bet its pretty....
 
Last edited:
dropped into a strong signal USS last night and just made it out alive. Shields went down and hull with 60% damage, all before my FSD had cooled down. So much for a high specked ASP. In my panic to run all I noticed was my aggressor was in a wing 6 of 6 (I thought wings were limited to 4 ? )
Elite has got very very DANGEROUS
 
Nice job Frontier.

One quick question to whoever read this...I press CTRL+ALT+Space but can't go into debug camera mode to see the ship from outside...Do I need to do anything else? Tried it in Private Group mode...not sure if it works only in Solo mode perhaps.

Thanks.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom