News
From PlanetsWiki
Contents |
[edit] Overview
Latest news concerning planets4. Usually from someone part of the coding team.
[edit] 23 March 2009
[edit] Operating system bugs and conflicts, Administrator rights
I have a few new answers for a few select problems that have been encountered.
First off id like to mention that both windows xp pro using service pack 3 and windows vista operating systems use the same security measures and thus are identical in they are problem resolutions being that of security issues. I also suspect this may be the case for XP home edition service pack 3 but not entirely sure.
There must be an understanding that program that changes overwrites or modifies files or folders such as updates or even running the programs needs to have security measures resolved to such a point that normal program operation is allowed to bypass the increased security.
Here a few examples of security preventing normal operations of the programs running, updating and even new installations.
Administrator rights. you first must have administrator rights if you don't it will cause problems. the initial installation of any new program must be set to "run as administrator" for it to run properly. this is done by right clicking the folder you wish you install, and selecting" run as administrator.
Not running as administrator when installing seems to cause lots of problems.
If your set to administrator and problems still occur. there are two resolutions that are against security related. First off you need to be sure that when u log on to your computer you do so with a password protected login. No password will prevent administrator rights from occurring. Secondly if after this you still have the problem check your user account information theres a box there is sometimes marked, its called " prevent alien programs from modifying files" if this is checked then planet will not only install improperly but it will cause other bad things to happen such as file sizes too small and additionally it will prevent race pack updates from actually changes the files to the new updated files.
make sure this box is unselected and that your user account is password protected. also ensure that anytime you install planets files or programs,(this includes Diplomat and VidiVici and alternate VCR as well) you install then with the run as administrator option.
I hope this helps all those of you who are new to planets and or new to a foreign operating system.
ProtoOperatingSystemAdminister
[edit] 18 March 2009
[edit] Pax & JOE Bug
Pax with JOE, will still bring all ships non-escorting, and all newly build ships. Host 213.38
The only way to not have ships jump, is to set them on NCH. Bug logged, issue # 418 (Drewhead)
Lord Lancelot 07:31, 18 March 2009 (CET)
[edit] 16 March 2009
[edit] Summary of some recent space combat issues
Hi!
1) Ignore disabled -> Ignore Disabled ships|bases
With the latest client we had the replacement
Ignore disabled -> Ignore Disabled ships|bases
Internally the old Ignore disabled used a bit 8 in a flag. The new Ignore Disabled ships|bases uses bit 15/16. The code in host was changed so that it has no compability difficulties. But the new client only affects bit 15/16. This means if you have a ships which had its bit 8 set and now you use the latest client you can't unset bit 8 any more. So although you uncheck the Ignore Disabled ships|bases still bit 8 is active resulting in a continuated ignoring of disabeld ships and bases. You have to go back to an older client, unset ignore disabeld and then everything should work as intented.
2) Stand off with stand off range > 0
A unit which is in an stand off mode with an stand of range > 0 can have problems to approach towards the primary target if this target is surrounded by too many units.
A strand off range > 0 can occur with the following settings:
- prefer bases - explicitly set stand off range > 0 - auto stand off mode of wings if no strike thru or C2PB was set - C2PB - Ships with are not set to stand off, quick strike, retreat or ram
So if you want to destroy a base or Dreadnought which is surrounded by guarding units you have to use a stand range of zero or RAM! Or strike thru. In the case of a base which should be attacked first you also should set the base as kill target or work with super weapons.
The reason fir this issue is that in stand off with range > 0 the secondary targets will inflict a repelling effect on the unit. The primary target inflicts an attracting effect with is 5 times stronger. So if there are more than 6 units around the primary target the net effect can result in a repelling respectively only circular movement component around the enemy group.
This issue turns out to be an effective method to screen bases and Dreadnoughts against long range attackers which want to take advantage by using stand off mode (especially PTT attackers). I will not remove it completely. I think of a factor of 9 instead of 5 because this method fits perfectly to the recent discussions about bases and Dreadnoughts.
3) Super weapons continue firing even if ignore disabled ships|bases was set.
GToeroe
