Originally Posted by LawsonThompsonReposting here for better visibility: Artemis 2.7 might crash at launch on PlayOnMac (perhaps other Wine systems as well). Not sure if that's an Artemis bug or a Wine bug.

The workaround: In the Wine/PlayOnMac configuration for Artemis, select Display and make the following changes:

GLSL Support: disabled

Offcreen rendering mode: fbo

Not sure what these actually do, but it fixed the problem! A 2011 MacBook Pro can run it smooth as butter now.

My experience on El Capitan 10.11.6 using an Nvidia GPU also demands that I enable Set Screen Options > Use Mac Driver Instead of X11. The wineskin crashes upon clicking "Start Game" on the resolution / windowed mode selection window unless that is checked. Even if that is enabled, it will sometimes crash at that same point, but will start up properly after another attempt or two.

Sorry to bug you, but we love your game and bought a copy around this time last year, I believe it was version 2.5. Anyways, we upgraded 5 PC's with version 2.7, my wife, 3 kids, and I all play together, and we can only get the new version to work on one of the five machines. I've tried everything I can think of...turned off virus protection, turned off firewalls, uninstalled, reinstalled, rebooted....any help you could provide would be greatly appreciated.

I suspect the problem is in the Windows 10 Program Files permissions. Find your Artemis folder in the Program Files and copy it either to your desktop or C:\Artemis. The upgrade should work no problem from there. __________________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.

BUG: during our 2.7 game today we found that when ships were destroyed, leaving wrecks, the wrecks spawned in a place other than where the ship was destroyed (still visible on the Helm and Weapons consoles, but usually in a different direction)

Originally Posted by Dave ThalerBUG: during our 2.7 game today we found that when ships were destroyed, leaving wrecks, the wrecks spawned in a place other than where the ship was destroyed (still visible on the Helm and Weapons consoles, but usually in a different direction)

I may be having a similar problem with a mission script. I'm creating several wrecks at specific coordinates, but the wrecks will spawn up to 1K-2K away. It may be a proximity thing with another object being too close? I haven't figured it out yet.

Originally Posted by Dave ThalerBUG: during our 2.7 game today we found that when ships were destroyed, leaving wrecks, the wrecks spawned in a place other than where the ship was destroyed (still visible on the Helm and Weapons consoles, but usually in a different direction)

I had a similar experience. At the time, I attributed the occurrence to some other ships having been attacked by a monster while my attention was elsewhere, but seeing your description, I suspect it's a bug.__________________CDR Callisto "Sandman" Bold Executive Officer of TSN Harbinger Shipwright of Project Harbinger (Seattle WA)

Originally Posted by MarkBellI suspect the problem is in the Windows 10 Program Files permissions. Find your Artemis folder in the Program Files and copy it either to your desktop or C:\Artemis. The upgrade should work no problem from there.

I tried this and it didn't work. I've tried uninstalling and reinstalling...running in windows 8 compatibility and nothing seems to work...

I tried this and it didn't work. I've tried uninstalling and reinstalling...running in windows 8 compatibility and nothing seems to work...

Help 😉

Okay, I never fixed this, but I did figure out that it's some sort of permissions issue. When I installed it on the machines that didn't work I only ended up with about 310 files in 23 Folders. On the machine that was working I had 846 files in 44 folders.

The work around I used was to copy the Artemis directory from the working machine to the other computers and boom! it works.

Originally Posted by Dave ThalerBUG: during our 2.7 game today we found that when ships were destroyed, leaving wrecks, the wrecks spawned in a place other than where the ship was destroyed (still visible on the Helm and Weapons consoles, but usually in a different direction)

Okay, I have reproduced this BUG:

Once asteroid fields have been created in a mission, any monsters created will be positioned to the upper right of the first asteroid field created. For each asteroid field created prior to the creation of the monsters, one monster will be relocated, always to the first asteroid field created. Once the number of monsters reaches the number of asteroid fields, they will be created at the specified position normally. If additional asteroid fields are later added, additional monsters will be relocated, to the first of the new set of asteroid fields.

I suspect this occurs in all game modes, but I tested it in script mode. Relocating the monster after it has been created seems to work fine.

BUG: beacons that Repel the Typhon (classic space monster) do nothing. That's because unlike all other monster types, the classic space monster is missing the AVOID_SIGNAL ai block at the end of its brain stack. Beacons that attract it work fine.

BUG: From my testing, the scripting command <if_damcon_members> no longer works in 2.7.0, in that the condition always evaluates to true regardless of what is actually the case. This is breaking mission scripts that worked in 2.6.0.

Originally Posted by Longbowman1346Comms hot keys no longer seem to work. When trying to use the numeric keys to process through the Comms ability, it no longer works. Only the mouse works on it. Anyone else try that?

Not a bug, you have to hold down Control with whatever button you want, so it doesn't interfere with Comms' ability to type in text messages.

Shortly after starting a level 5 solo Siege mission, we were set upon by a wing of TSN fighters! They showed up hostile (red) on radar and didn't have any science scan description which indicated malice. Didn't follow through to see where they came from or if there was a pirate carrier or something.

Originally Posted by Dave ThalerBUG: during our 2.7 game today we found that when ships were destroyed, leaving wrecks, the wrecks spawned in a place other than where the ship was destroyed (still visible on the Helm and Weapons consoles, but usually in a different direction)

I had a similar experience. At the time, I attributed the occurrence to some other ships having been attacked by a monster while my attention was elsewhere, but seeing your description, I suspect it's a bug.

Add a third report to this bug. I thought it was random additional drops. Running a Windows Desktop with a clean install of Windows 10 pro.

Insert Photos

Web address (URL)

Image URL

If your URL is correct, you'll see an image preview here. Large images may take a few minutes to appear.
Remember: Using others' images on the web without their permission may be bad manners, or worse, copyright infringement.