Was there a beta test for 1.6?
- Thread starter Jay8ch
- Start date
I only used 2.1, but I seem to recall there was a 1.6 beta option too.
There was a 1.6 beta client, but it's the same beta since both versions run on the same beta server.
It's the same code base...1.6 is 2.1 just with stuff disabled.
The mission bugs I've seen mentioned are also in 2.1 as far as I can tell even if I personally haven't had any major issues. The only thing I've come across is that I couldn't deliver a mission at a station since there was no mission board and this isn't necessarily a bug per se. The station could have been "UA bombed" or had certain services disabled due to other factors. It IS however unclear and there should be obvious information given to inform the player of what's going on in cases like this. (Unless is was a bug after all
)It's the same code base...1.6 is 2.1 just with stuff disabled.
The mission bugs I've seen mentioned are also in 2.1 as far as I can tell even if I personally haven't had any major issues. The only thing I've come across is that I couldn't deliver a mission at a station since there was no mission board and this isn't necessarily a bug per se. The station could have been "UA bombed" or had certain services disabled due to other factors. It IS however unclear and there should be obvious information given to inform the player of what's going on in cases like this. (Unless is was a bug after all
I really don't want to read anything about a station being UA bombed again. Having absolultely no information or options regarding a mission is a bug, and an incredibly annoying one at that. This stuff worked in 1.0 for heaven's sake.
Old features can break when new features are introduced, such is the wonders of game design.
1.6 and 2.1 is the same game. It's the same code, the same galaxy, the same missions the same same. The only difference is that 2.1 players can land on planets but I don't see how this is related to missions not working.
Last edited:
All mission bugs i have seen people seeing in live version of 2.1/1.6 were reported during beta. I saw some and reported some on bug reporting section during beta. Many said that it wasn't ready to be released, but they still released it without fixing those bugs we reported during beta.
I tested 1.6 missions in betas 2 to 6 and reported quite a few issues, mission bugs in the main. I did do a short time in 2.1 but mainly I tested 1.6 (64-bit version).
So yes people tested the 1.6 in betas and reported the issues. What F D did with the reports is anyone's guess but since they seemed more interested in Engineers they seem to me to have concentrated on the modified equipment aspects (and coincidentally totally ignored the effect modded weapons on the AI would have on 1.6 players).
Agreed, the Bulletin Board menu could be there but in red if there is a UA bombing, for example. It's here, it's just not usable for the moment.It's the same code base...1.6 is 2.1 just with stuff disabled.
The mission bugs I've seen mentioned are also in 2.1 as far as I can tell even if I personally haven't had any major issues. The only thing I've come across is that I couldn't deliver a mission at a station since there was no mission board and this isn't necessarily a bug per se. The station could have been "UA bombed" or had certain services disabled due to other factors. It IS however unclear and there should be obvious information given to inform the player of what's going on in cases like this. (Unless is was a bug after all
You can check if it was a bug by comparing the station with the list released by Sandro, I believe, of the UA-bombed stations, and then checking the system/galaxy map to see if the system is in lockdown, which now does affect stations considerably. If those conditions are not met, file a bug reportIt's the same code base...1.6 is 2.1 just with stuff disabled.
The mission bugs I've seen mentioned are also in 2.1 as far as I can tell even if I personally haven't had any major issues. The only thing I've come across is that I couldn't deliver a mission at a station since there was no mission board and this isn't necessarily a bug per se. The station could have been "UA bombed" or had certain services disabled due to other factors. It IS however unclear and there should be obvious information given to inform the player of what's going on in cases like this. (Unless is was a bug after all
If the system/faction is in lockdown, you can check!
- - - - - Additional Content Posted / Auto Merge - - - - -
That's not how it displayed in Irens Dock, Manite, which has been UA bombed. It just wasn't there.
Last edited:
You can check if it was a bug by comparing the station with the list released by Sandro, I believe, of the UA-bombed stations, and then checking the system/galaxy map to see if the system is in lockdown, which now does affect stations considerably. If those conditions are not met, file a bug report
If the system/faction is in lockdown, you can check!
So you think it's acceptable that you have to search forums for an obscure list about something not mentioned in the game before taking on any missions? Shall I reverse engineer the code and mod my game so that if a station has been "UA bombed" there's a tiny little clue when you get there? Maybe some bomb damage perhaps? Maybe some broken lights? Maybe even just a tiny piece of text that says "This station has been UA bombed. Sorry for in the inconvenience."
Stop trying to dress this up as anything other than an infuriating waste of a gamer's time. I'm disgusted as this so called missions overhaul. It's disgraceful.
Last edited: