Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
MarkBell

Avatar / Picture

Administrator
Registered:
Posts: 1,935
Reply with quote  #1 
If you have bug reports for 2.7.4, please put them here!  Do note that with 3.0 under development, there probably won't be a lot of new functionality in 2.X, although Thom is still looking at buggy behavior.
__________________
Note - this is in no way intended to be an official position of Thom or Artemis, as I am not an official representative of the creator or game.
NoseyNick

Avatar / Picture

Registered:
Posts: 79
Reply with quote  #2 
[ In retrospect, didn't belong in the News thread. moved here ]

When run on Linux under WINE ... what? isn't that how everyone runs it? [wink] Well OK, but it's how I normally run it myself, and how my popular AWS Artemis Nebula servers run it...
Stdout is filled with A LOT of "Simulation::Tick-304  Player::Tick-218  Simulation::Tick-308" stuff, which I think also hurts performance a bit.

This is roughly the same as running Artemis.exe from a command prompt instead of double-clicking on it.

I wonder whether some of useDebugConsoleWindow still exists and is going to stdout instead of the DebugConsoleWindow, even when useDebugConsoleWindow=0?

I seem to be able to regain performance by redirecting to /dev/null (I think cmd-prompt calls this NIL: or NUL: or something?) but then I might miss any other errors (EG occasional direct3d warnings)
NoseyNick

Avatar / Picture

Registered:
Posts: 79
Reply with quote  #3 
Minor bug report:  controls.ini:
  END_SIMULATION             = UI_INPUT_KEY_E
... is the same as the undocumented "E for AI"   [smile]

I think this began in 2.7.2? I may be mistaken.
NoseyNick

Avatar / Picture

Registered:
Posts: 79
Reply with quote  #4 
Not new to 2.7.4 but definitely still present in 2.7.4:

There seem to be many situations under which a client can connect, claim helm/weap/eng, then disconnect "uncleanly" (EG unplug network cable, forcefully switch off WiFi, various other network errors, or close lid and "put laptop to sleep"). Some time later, other tools imply that the TCP socket HAS been closed at the server end, but the stations are still "claimed" and a new client can't connect to them, frequently leaving ships "stranded" with no helm or weapons, or fixed sub-optimal eng settings.

Would definitely be much appreciated if any TCP socket errors could close the socket and free up the corresponding station(s)

Many thanks!
notsabbat

Avatar / Picture

Registered:
Posts: 1,266
Reply with quote  #5 
Hot Keys. All the hot keys.
__________________
-Captain of the TSN Gungnir JN-001
-Eastern Front online group member
-My continuing bridge build:
http://artemis.forumchitchat.com/post/immersion-bridge-build-in-progress-7335195?pid=1290158413
Mike Substelny

Avatar / Picture

Administrator
Registered:
Posts: 2,351
Reply with quote  #6 
Quote:
Originally Posted by NoseyNick
Not new to 2.7.4 but definitely still present in 2.7.4:

There seem to be many situations under which a client can connect, claim helm/weap/eng, then disconnect "uncleanly" (EG unplug network cable, forcefully switch off WiFi, various other network errors, or close lid and "put laptop to sleep"). Some time later, other tools imply that the TCP socket HAS been closed at the server end, but the stations are still "claimed" and a new client can't connect to them, frequently leaving ships "stranded" with no helm or weapons, or fixed sub-optimal eng settings.

Would definitely be much appreciated if any TCP socket errors could close the socket and free up the corresponding station(s)

Many thanks!


Thanks for reiterating this one. I believe that if it's not fixed the unclaimed console bug will be a major problem at Armada V, which is less than three months away. In my experience closing a laptop lid is a common practice that always seems to lead to disaster with Artemis. I know "always" is an exaggeration, but I have seen it disrupt so many games for so many players that I get twitchy whenever I see someone close a laptop.

__________________
"The Admiralty had demanded six ships; the economists offered four; and we finally compromised on eight."
- Winston Churchill
NoseyNick

Avatar / Picture

Registered:
Posts: 79
Reply with quote  #7 
Quote:
will be a major problem at Armada V, which is less than three months away. In my experience closing a laptop lid is a common practice that always seems to lead to disaster with Artemis


Hey at least Armada is on a LAN. We hit it about 4 times when playing the most recent afternoon of TSN Trans-Canada games because all our players are across THE INTERNET, and all it takes is some router to reboot, DSL to drop/reconnect, cable ISP to flush NAT tables, or 5G hotspot to "helpfully" drop/reconnect to save your cell bill, and an entire ship changes IP addresses and loses their connections. About the best we could do was say "Oh sorry, please take $SPARE_SHIP", which also isn't possible when we have 8 ships   [crazy]

I am somewhat reminded of DaveT's "First Galaxy Problems" but hey   [biggrin]

Many thanks! I know TCP stack programming is a pig, I've done more than my fair share.    [frown]
NoseyNick

Avatar / Picture

Registered:
Posts: 79
Reply with quote  #8 
Techbear says:

Quote:
elite ships (skaraans) now have two more special powers. One is a shield frequency scrambler, that randomly changes shield bands. The other is just like the normal teleport, but backwards instead of forwards.


... but mission-file-docs.txt doesn't mention the new const int ELITE_[something] = 2048 | 4096
Dave Thaler

Registered:
Posts: 465
Reply with quote  #9 
Same bug reported on 2.7.2 still exists in 2.7.4:

The controls.ini has this, which doesn't work:
VOLUME_COMMS_UP            = UI_INPUTHOME

It should instead be this:
VOLUME_COMMS_UP            = UI_INPUT_HOME

Here is the fixed controls.ini which also fixes several other typos in the file, as posted to the 2.7.2 thread.

Dave Thaler

Registered:
Posts: 465
Reply with quote  #10 
The following issues I reported on earlier Artemis versions still exist on 2.7.4:

ISSUE: On the Comms screen, by default no categories are selected, resulting in no comms messages shown below the categories.  However, after selecting and deselecting any category (leaving no categories selected), results in ALL comms messages being shown below the categories.   Seems like the result should be the same, whatever it is.

ISSUE: When selecting a singleseat ship type, the left arrow stops at Unassigned as opposed to being circular.  This is unexpected since the right arrow gives circular behavior, as does the left arrow when selecting a capital ship type.

ISSUE: Singleseat ship names are "saved" on the server screen if you go Back and click Customize Ship again, you see what you just entered.  However, whenever you click Customize on a client's Helm screen it instead clears all the singleseat ship names.


ISSUE: Instead of being in alphabetical order, scripted missions are in reverse alphabetical order, so you have to hit the back arrow to go forward through the list, and the forward arrow to go back through the list.
Dave Thaler

Registered:
Posts: 465
Reply with quote  #11 
BUG (reported on 2.6, still present): F1 on Data screen gives fighter help text that isn't shown in the fighter console help text.  Specifically, it says:

 Fighters have homing missiles; shuttles do not.
 Dock with your carrier to reload.
 Missiles auto-home on the nearest target; careful where you fire them.
 
This text needs to be moved to the Fighter console F1 help screen.

Also the Fighter console F1 help screen is showing some Comms help text in addition to some (different) Fighter help text.  Also the Comms console F1 help screen is showing some (yet a third different set of) Fighter help text.


Dave Thaler

Registered:
Posts: 465
Reply with quote  #12 
BUG (reported on 2.7.0, still present): The chase CAM button doesn't seem to work on any ship except Artemis.  That is, the ship itself is always visible on the ship's main screen clients and clicking CAM has no effect.
Dave Thaler

Registered:
Posts: 465
Reply with quote  #13 
BUG (reported on 2.6, still present): Timers continue to run and count down while the simulation is paused.
Dave Thaler

Registered:
Posts: 465
Reply with quote  #14 
BUG (reported on 2.6, still present): When a ship other than Artemis has its rudder not centered but has 0% maneuverability due to damage or no power to maneuverability so it cannot in fact turn, the ship is still shown to other player ships' Helm, Weapons, Science, Captains Map, Data, Game Master, and Vis consoles as spinning in place.   (The server's main screen correctly shows it as stationary, but any main screen client will not.)  Artemis works correctly, and is not shown as rotating to Intrepid, but when Artemis looks at Intrepid, the bug is evident.
Dave Thaler

Registered:
Posts: 465
Reply with quote  #15 
ISSUE (reported on 2.7.0, still present): It seems unrealistic that basis will follow pirate ship orders to build specific ordnance.   (Previously bases also responded "Docking crew is ready" when asked to stand by for docking even though you couldn't dock.  That has now been fixed, but bases should similarly ignore requests to build ordnance from ships they won't let dock.)
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.