viewizard / astromenace Goto Github PK

Expected Behavior

In begining of second mission there is set of fighters, escorting cariers, initially facing towards player movement direction. At some distance from player they turn and begin to shoot in sequences of 3.

Actual Behavior

Only for those, in escort (including final 6 after convoy deselerating) - first shot goes forward, but all next including two in first salvo go backward, this repeats for each escort fighter independently, not for entire escort. Attacking wave in the end doesn't have such problem. Don't remember is it case in later similar scenarios.

Specifications

Laptop With Full Specs: Lifebook s760
Operating System: Arch Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel-Version: 5.5.13-arch2-1
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz
Memory: 3.6 GiB of RAM
GPU Acceleration: NONE
GCC Version: GCC (Arch Linux 9.3.0-1) 9.3.0

• Game Version:
  Your latest commit when I cloned the master branch

Configuration Files

config.txt
PilotProfiles_1.4.txt

Logging File

log.txt

After Opening the game, I see the loading screen. After the loading finishes the music stops and the game stuck in the loading screen. If I use alt+f4 to kill the application, I get a Not Responding error from KDE plasma and I just click kill the application.

Expected Behavior

I expect high-quality code repositories to do Continuous Integration tests, such as by GitHub Actions. The results of these builds can be seen in an 'Actions' tab (next to the 'Code' , 'Issues', 'Pull requests', etc. tabs)

Actual Behavior

The tab 'Actions' is removed. There is no CI at all.

Steps to Reproduce the Problem

1. Go to https://github.com/viewizard/astromenace
2. Search for the tab 'Actions': it is not there

Misc

I do volunteer to add and maintain this. I would enjoy to see one of my favorite games to show its high quality code :-)

Could you add a separate Screenshots page to your website?
So I will be able to point to this page here:
https://salsa.debian.org/games-team/astromenace/blob/master/debian/upstream/metadata
Some details about Debian upstream metadata you may find here:
https://wiki.debian.org/UpstreamMetadata

Crash Log - https://gitlab.com/snippets/1720475

Tested on latest git build. There is a chance that this is due to my system configuration, I will run some more games with this exact same system configuration and find out if it is crashing in only AstroMenace.

The game crashes on level 9, at semi-random times?

Crash log was saved by running "astromenace >out 2>&1"

AMDGPU - Radeonsi Mesa 18 - ARCH

(As an aside, enabling GLSL with shadows off brings my FPS down from 750 to 15. Then enabling 8x8 increases it to 50. Very strange. Every other graphics setting I can run at max. RX480, Ryzen at 4 ghtz.)

Another thing, level 9 is almost impossible at %143 difficulty, Maybe enemy missiles need nerfing and enemy lasers need to be buffed?

Expected Behavior

I expected, that mechanics affects targeting in both H/V direction. And OTC handles only target selection for turrets (probably missile locking as well). According to what I just discovered, turret rotation speed is reflected at visible turret rotation too, and thus visible horizontal rotation should not be instant (this is first thing, that I discovered after looking how different vertical weapon rotation is).
Both OTC and turret mechanics must present to be useful. Complete removal of one should make another useless.

Actual Behavior

It seems, despite naming, OTC controls horizontal aiming only, while turret mechanics - vertical. I got successfuly working horizontal aiming with removed mechanics. Of course, no vertical correction was done, and thus I discovered, that most (at least first) targets at first level are placed slightly lower (so that all shots go above without correction), though not enough to let player ship just pass above. I remember, that something changed in auto-aiming since 1.4.0 (difficulty?), but could not find what, before these observations.

Steps to Reproduce the Problem

1. Try with missing OTC - vertical targeting works. Aiming speed depends on mechanics.
2. Try with missing mechanics (but with OTC). Horizontal auto-aim works, (re)aiming instantly, but no vertical aim (shots go above all starting enemies).

https://flathub.org/apps/com.viewizard.AstroMenace

Is it maintained by you? Should be mentioned in the README.

When playing on a dual-monitor setup, the mouse cursor can leave the fullscreen window and interact with windows on the other monitor. I don't know if this will be easy to fix, it's not a big problem anyway. Just thought I would let you know. I hope you have a good day.

Expected behavior: mouse should only leave window when it isn't attached to ship control. When there is a cursor on the screen, it can leave the window, that's fine. When there is no cursor on the screen and my mouse is controlling the ship, the input should be locked within the window.

Arch
AMDGPU-all-open
Gnome3

Unfortunately I have missed latest releases of your game because they were not uploaded to https://sourceforge.net/projects/openastromenace/files/ where Debian infrastructure was looking for updates.

I will use this git repo for the future updates of Debian package. But probably it would be a good idea to keep SourceForge project in sync with GitHub. Just in case.

Expected Behavior

the game is in english but i wish put in spanish, luckly i realised there are translations available at crowdin

Actual Behavior

• there is no indication anywhere on how to install the translation file
• i cant download the file from crowdin FREELY (as "libre", not as "gratis") because it obligues me to login before. according the gplv3 in which code and assets are licensed (according LICENSE.md file), it shouldn't impose any restriction or constraint to access sources

Steps to Reproduce the Problem

• try to download the translation file directly and anonymously, and i cant (i love my privacy and my free will)
• even if i would have the file, i haven't found any instruction on how to install and make it work with the game

Specifications

i think my pc specs are meaningless in this case because the game runs me marvelous and i just want to switch the language (i am chilean), but anyway i have:

• astromenace 1.4.1 for windows, downloaded directly from your website
• windows 8.1 x64 spanish (dont like 10, i like 7 but now is a bit outdated)
• dell precision t7500 (intel pentium xeon 3.5ghz, 12gb ram, 1tb sata hd, dvd recorder, hd audio, gigabit lan, etc)
• nvidia geforce gtx1650 4gb gddr5
• standard 1080p monitor, keyboard and mouse, etc.

this game likes me a lot... i hope you document how to localize the game, and do something with the register/login requirements to download the translations

Tested Windows 64bit build - MSYS2+MinGW 64bit.
Segmentation fault at game start (looks like some init or VFS issue), need investigate this more carefully.

Tested on RPI4, looks like initial configuration at first game start by hardware detection should be revised for ARM.
Current initial configuratin logic for ARM enable shaders and antialiasing, so, I see 4-5 FPS only at 1920x1080 resolution (by default current initial configuration logic will use display resolution at full screen if possible).

The game does not open for some reason

Actual Behavior

error: XDG_RUNTIME_DIR not set in the environment.
main(): Couldn't init SDL: No available video device

Steps to Reproduce the Problem

I just cloned the repo and followed the steps that you wrote

Specifications

• Operating System (with version, if you know it):Debian 10
  • For example: Windows 10 Home / macOS 10.9 / Ubuntu 18.04
• Hardware Specifications (optional, if you know it):12 GB RAM, Integrated videocard, I7 7th generation, notebook HP

I would really love to play your game, I hope you can help me

These are i386 only and do not seem to affecty amd64.

src/core/vfs/vfs.cpp:450:22: warning: comparison of integers of different signs: 'long' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
                if ((Pos + offset) > Size)
                     ~~~~~~~~~~~~  ^ ~~~~
src/core/vfs/vfs.cpp:456:14: warning: comparison of integers of different signs: 'long' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
                if (offset > Size)
                    ~~~~~~ ^ ~~~~
src/core/vfs/vfs.cpp:462:31: warning: comparison of integers of different signs: 'long' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
                if ((offset < 0) || (offset > Size))
                                     ~~~~~~ ^ ~~~~
3 warnings generated.

Expected Behavior

Different ships (at least of different types) should have different basic speed. At least it is how it was in 1.3.2 (not sure about 1.4.0). E.g. I can't imagine fighter as slow as bomber.

Actual Behavior

While playing 1.4.1, It appeared later, that starting fighter speed is not just lowered, but is same as for starting bomber (that one wiht cost 1500 and 5+1+1 weapon slots). Previously I tried full gameplay with this version, but can't remember wether I got devastator - in original game it had lowest speed with basic engine, but I don't remember if it so in current version (no saves with enough money to try it).

Steps to Reproduce the Problem

Nothing special. Basic bomber could be bought after selling basic missile launcher (btw, not best choice for first mission, more useful at raider bases).

Specifications

astromenace 1.4.1 release
OS - gentoo (ebuild in personal overlay, version bumped from portage openastromenace version)

Game Configuration (optional)

config.xml: https://gist.github.com/nick87720z/dd832a8802cb7b73edd095e19d7238dd
PilotProfile_1.4.data: https://gist.github.com/nick87720z/2feb73039b2f9f59b7374a8a27685569

A screenshot explains it much better:

I'm using the latest (auto)-release: https://github.com/viewizard/astromenace/releases/download/1.4.2-1781/astromenace-osx.tar.gz

What could be the issue here?

There's 1.4.2-1781 tag in the repository. Is this a new official release? If so, why's it not mentioned on https://viewizard.com/download.html?

My locale settings:

% locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_COLLATE=C
LC_TIME=C
LC_NUMERIC="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES=C
LC_ALL=

This is tuned in a way that applications would handle Russian properly (LC_CTYPE), but interface would stay unlocalized (LC_MESSAGES). Astromenace runs in Russian, so it reads locale settings incorrectly. LC_MESSAGES is the locale entity responsible for the UI language, so taking standard locale selection logic, it should act as follows:

• if LC_ALL is defined, take UI language from LC_ALL (e.g. LC_ALL overrides everything)
• otherwise, if LC_MESSAGES is defined, take UI language from LC_MESSAGES
• otherwise, if LANG is defined, take UI language from LANG (e.g. LANG is the default for all LC_* aspects)
• otherwise, fallback to default (English)

FreeBSD 10.4 (does not affect newer versions).

src/config/config.cpp:535:65: error: no viable conversion from 'std::array<int, config::MAX_PROFILES>' to 'value_type' (aka 'int')                                                                                                                          
        static std::array<int, config::MAX_PROFILES> DifficultiesArray{CalculateDifficulties()};
                                                                       ^~~~~~~~~~~~~~~~~~~~~~~
src/config/config.cpp:535:65: warning: suggest braces around initialization of subobject [-Wmissing-braces]
        static std::array<int, config::MAX_PROFILES> DifficultiesArray{CalculateDifficulties()};
                                                                       ^~~~~~~~~~~~~~~~~~~~~~~
                                                                       {                      }
2 warnings and 1 error generated.

The cause is likely an old clang/libc++ (3.4.1), but since it may hit someone else it might be a good idea to rewrite this as either

static std::array<int, config::MAX_PROFILES> DifficultiesArray = CalculateDifficulties();

or

static std::array<int, config::MAX_PROFILES> DifficultiesArray(CalculateDifficulties());

Expected Behavior

Astromenace runs smoothly on MacBook Pro 2019

Actual Behavior

Steps to Reproduce the Problem

1. Compile Astromenace from source as being said in Readme
2. Run Astromenace

Specifications

astromenace.txt

• Operating System (with version, if you know it):
  • macOS Ventura 13.1
• Hardware Specifications (optional, if you know it):
  • 2.3 GHz 8-Core Intel Core i9
  • AMD Radeon Pro 5500M 4 GB
  • Intel UHD Graphics 630 1536 MB
• Video Drivers (optional, if you know it):
  • ??
• Game Version:
  • Latest master

What bothers me is that it says about software renderer:

Vendor     : Apple Computer Inc.
Renderer   : Software
Version    : 1.1

Files location:
astromenace.zip

Expected Behavior

They spaceship should move in the up/down/left/right when the up/down/left/right arrow key is pressed

Actual Behavior

Nothing happens.I can fire both my weapons but the ship is fixed in one place

Steps to Reproduce the Problem

1.Install a Clean Copy of Astromenance
2.Launch the first mission
3.The ship does not move

Specifications

• Operating System (with version, if you know it):Ubuntu 18.04
  • For example: Windows 10 Home / macOS 10.9 / Ubuntu 18.04
• Hardware Specifications (optional, if you know it):Intel core i7,Nvidia Geforce 840M,8 GB RAM
  • For example: Intel i7 8500, 8GB memory, Nvidia 760 GTX with 2GB memory
• Video Drivers (optional, if you know it):
  • For example: Nvidia drivers 390.42 / xf86-video-amdgpu 18.0.1
• Game Version:Version 1.3.2
  • You can find it in the left bottom corner in the game menu.
• Git Commit (optional, for test/self made builds only):

Game Configuration (optional)

Please provide your AstroMenace game configuration (config.xml and PilotsProfiles_N.N.data, where N is number).

Files location:

• Windows: C:\Users\{user name}\AppData\Roaming\Viewizard\AstroMenace\
• Linux: ~/.config/astromenace/

Note, these are plain text files, you could use https://gist.github.com/ (or any other service) and provide links, or change the files' extensions to '.txt' in order to attach them directly to the Issue.

Please, DO NOT copy files content to the Issue itself.

Terminal Output (optional, Linux)

Launch AstroMenace from terminal with logging into file. For example:

$ ./astromenace > ~/Desktop/log.txt

log.txt on your Desktop is the result.

You could use https://gist.github.com/ (or any other service) and provide a link, or attach the file directly to the Issue.

Please, DO NOT copy file content to the Issue itself.

HI dear author,
It's truly a honor to write a letter to you, I'm build your project nowadays and found the error when building as following, I wonder if there is a chance that you know the reason? :)

thank you
best regards to you
William