List of Bugs from AoY Tribble Patch

andyphamx

A list of some things I have seen so far and I would like to know if anyone else has experienced the following:

1. Text at character creation

When creating a character and selecting Andorian as the preferred race, the race chosen label displays "TOS_Andorian"
This occurs for both the male and female option.

Note that I just found this text bug funny.

2. Graphical Bugs

First off, note that I ran the game at minimum graphics.

• Female NPCs have their decolletage exposed when zooming out the camera at a specific distance from them. The map location is not a factor.
• Shuttle bay doors do not open and the shuttle just flies through unopened shuttle bay doors
• At the TOS bridge, I get 50 frames per second (fps), when I am at the area where I first come down to the planet (Taurus II), my frame rate drops to about 16 fps, as I progress through the mission the frame rate got better, up to 38 fps. I stopped at the mission "Bull by the horns" due to a bug described in the post in the link in the previous point.

1st Edit

After the patch that fixed the "Bull by the Horns" mission objective "Equip Phaser Rifle," the following bugs were found within the same mission.

• Doctor Phineas Grogon does not walk properly to the weapons crate, thus takes a significant amount of time for the player to complete the mission objective, "Distribute Phaser Rifles"
• The mission objective "Shoot at alternate debris" requires the player to manually shoot the debris since it cannot be targeted.
• The mission objective "Send Survivors to Wreckage" cannot be completed due to the missing 4th survivor (Researcher Halleck). After logging out and logging back in, Researcher Duncan appears at her spot as if the player never sent her to the ship wreckage, but is not at the objective indicator circle and cannot be interacted with. In addition, Doctor Phineas Grogon is not found within the ship wreckage with Doctor Muller sometimes (Issue was resolved after logging out and back in several times). Note that the missing 4th survivor bug was resolved by creating a new character.
• The game crashes when completing the mission objective "Scan for heat Signatures," but the progress can be made after restarting the game. Crashes do occasionally occur afterwards though.

In the mission "Of Sheep and Wolves," my frame rate starts off at around 19 fps and only improves to at most 29 fps by the time I reach the USS Enterprise.

Also, the game crashes when the player warps into sector space from ESD.

That is all of the bugs From Taurian Affair that I have found

I will continue to mess around and see if I can find anything else.

xaviermace86

Specifying your FPS doesn't really do much good without your hardware info.

andyphamx

xaviermace86 wrote: »

Specifying your FPS doesn't really do much good without your hardware info.

OS: Windows 10 Home 64-bit
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 CPUs), ~2.6Ghz
Graphics card: NVIDIA GeForce GTX 860M

lucho80

andyphamx wrote: »

OS: Windows 10 Home 64-bit
Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 CPUs), ~2.6Ghz
Graphics card: NVIDIA GeForce GTX 860M

That FPS drop is definitively an issue considering you can run this game on 2010 modest gaming hardware.

zebulongiles

I think this is the proper topic for this: My game crashed to the desktop when scanning for heat signatures after electrifying the hull.

sharpie65

In the "Shadow of Cestus", the Romulan ships that appear after disabling the Gorn ship (via a cutscene) appear as Mogai/Valdore-class ships. However, after the aforementioned cutscene they correctly show as "Khenn-class cruisers".

EDIT: Also, before you beam down to the surface of Edren IV (before/during the dialogue with Capt. McKinnon) there appears to be a Gorn Zilant Battleship.

dirlettia

Killing the Gorn on Edren I got a personal shield MK II drop although the icon is not for a personal shield and instead is a green box with the word Primary on it. It still equips as a shield though.

Edit: When starting the Cestus mission for a second time on replay it starts off as 'beam to your ship' as the first objective making starting the mission from space a problem. Any chance of removing this?

bergins

Had the same "Beam to Your Ship" issue today. Found that going back to ESD and beaming back up solved it.*

*This is a workaround, it's still a bug.