Public Beta for Legends v1.7.0.16 now Available!

[WoodMan]

Every time I start a new game I get the latest patch be it official or beta. The official patches are basically a culmination of many beta patches. I wouldn't say it is vital to get it right away, wait until you finish your current game then go for it. [;)]

[Haree78]

ORIGINAL: Bleek

How do these beta patches work, am I ok to stick to the official release or am I missing out and 'game changing' additions by not testing the beta patches?

As Woodman says stick with your current game but if you are thinking of starting a new one the current beta is well worth using. 1.7.0.15 is a lot better than the current official version.

[michaelm75au]

ORIGINAL: Gzu

ORIGINAL: Shark7

ORIGINAL: MartialDoctor




Actually, I was starting to think this was an issue as well.

Actually, I think there is little debate, it seems to be more of a fact.

I made a serval tests. In my games, engine just apply one standard* policy for all the empires. No matter if i use customization folder or edit orginal data files.

*standard = all set to normal/balanced/etc.

I recall some issue around permissions on these files for customomisation. If not read only, they weren't accessed.[&:]
Maybe I am mixing this up with some other set of files.

[ASHBERY76]

ETA on next beta?

[oxenshtrudel]

ORIGINAL: ASHBERY76

ETA on next beta?

Soonish. The next update is undergoing closed tests right now. Unless something major is found it will most likely be released soon.

[Erik Rutins]

Hi Everyone,

The new 1.7.0.16 Public Beta Update for Distant Worlds: Legends is now available. We hope this will be the last public beta update before this becomes an official update in a week or two.

For those that are willing to help us give this a test before it becomes official, it is very much appreciated.

The updated change list is in the first post in this thread.

Regards,

- Erik

[ASHBERY76]

Nice timing.

[Speedy2511]

Hey, thanks for the update

Greetings from Germany
Nico

[tjhkkr]

Thank you!

[Igard]

Thanks for the update, an hour played looks good so far!

[MartialDoctor]

Nice work. Good to have a new update here [:)]

[chrono280]

Wanted to report a bug (at least I think it is a bug) in 17.0.16:

If you select a design, then select Manually Upgrade, then, if you do not change anything and just hit CANCEL instead of SAVE, the design is automatically marked as obsolete. I don't know if this happens in earlier beta builds because I haven't done as much playing in those.

Hope this helps, thanks again for making a terrific space 4x [:)]

[vengen]

I've noticed a few things that may be bugs in 1.7.0.16 (but I've played so infrequently in the last two years that they may be things that I've somehow messed up in my settings):

1 - Started a game as Wekkarus and the default escorts were the size of frigates, the default frigates were the size of destroyers, and the default destroyers were so large that I could not even build them.

2 - My next door neighbor Hakonish kept removing its trade embargo, then immediately re-imposing it. Both messages appear at the same time - the removal above the re-imposition. This stopped once I built a bunch more warships.

3 - I can't build them yet, but I have a bunch of non-obselete designs for Cruisers and Battleships in my design screen.

4 - This has been happening since at least 1.7.0.12, but sometimes I get an exotic resource on two different planets - it's usually Zentenaba Fluid. Is that WAD or a bug?

I'm not seeing anyone else post bugs, so I'm thinking that this is probably an issue with my machine, a corrupt install, or I've messed up my settings?

Edit - On second thought - does this belong in the tech support forum?

2nd edit - Post moved to the Tech Support Forum.

[MartialDoctor]

Yeah... you guys need to place those bugs in the tech forum section [:)]

[scotten_usa]

ORIGINAL: chrono280

Wanted to report a bug (at least I think it is a bug) in 17.0.16:

If you select a design, then select Manually Upgrade, then, if you do not change anything and just hit CANCEL instead of SAVE, the design is automatically marked as obsolete. I don't know if this happens in earlier beta builds because I haven't done as much playing in those.

Hope this helps, thanks again for making a terrific space 4x [:)]

Old bug, been around forever....

[chrisrox]

Got a few bugs to report in, starting with the biggest.

1. Ships starting with no weapons
Had a big problem with all military ships for all races as well as pirates receiving no weapons at game start. So i started experimenting a bit with the policy files under Distant Worlds\Policy\. Moving or deleting these solved the problem, as well as using my ingame customised policy file with the starting race name. So i compared the "in game" generated file with the others and the only difference i could find was that all decimal-values used , in the one that worked and . in the others.

Solution to 1
Replaced all . with , in all race policy files and now it works like a charm.

2. Ingame generated policy file doesnt save the following values:
Allow sabotage mission: Destroy base
Allow sabotage mission: Assassinate character
When establish new colony, immediately build this base
Never recruit troops until colony population reaches

3. DesignComponentAreaWeaponsSpaceports is set to N in policyfiles and cant be changed ingame.


Love the game!!!


!!!!Post moved to the Tech Support Forum!!!!

[ASHBERY76]

ETA on next beta.The autodesign isssue is pretty serious.

[endoric_MatrixForum]

ORIGINAL: ASHBERY76

ETA on next beta.The autodesign isssue is pretty serious.

i second this

[WiZz]

I think, it was the last patch...

[endoric_MatrixForum]

wow that would put matrixgames on my 'never buy from game company list' that is sadly full of indy companies.