1. #1
    UbiDomZ's Avatar Community Manager
    Join Date
    Aug 2017
    Posts
    555

    Star Trek: Bridge Crew KNOWN ISSUES - Updated 8/1/18

    The descriptions below are the actual bug entry (JIRA) descriptions minus some tags which we use. Naturally the entries we provide the developers to investigate have a great deal of addition detail beyond this including exact steps QA staff have found recreates it, the frequency and repeatability, platforms affected, build versions found on, etc. Not that if an issue has been recently reported, it may not yet appear on this list as it takes some time for us to update.

    GENERAL GAMEPLAY

    FIXED

    • NAME: Missing enemy designations
    • DESCRIPTION: Enemy ships of the same class are missing identifiers in their names
    • STATUS: Bug recreated by QA, under investigation

    NO FIX - Difficult to reproduce and extremely rare... has no measurable gameplay impact

    • NAME: Location flicker
    • DESCRIPTION: Local Map flicks to the previous location for a second after Impulse or Warp
    • STATUS: Bug recreated by QA, can be difficult to reproduce, under investigation


    FIXED

    • NAME: Scanning errors
    • DESCRIPTION: Anomaly in Sarza has no scanning result
    • STATUS: Bug recreated by QA, doesn’t always happen. Note that this anomaly may not appear initially on the captain's navmap or tactical's navmap, so players may need to fly around to find it. Under investigation



    • NAME: Mic Check Priority
    • DESCRIPTION: The Play Together function will not circumvent the mic check for nonVR client players in the party. This causes an issue where the player can not enter the lobby and remains on mic check screen that they can not pass. While in a PSN party, all the input audio is rerouted to that party chat instead of the game. Thus, the nonVR clients can not pass the mic check as no audio is entering the game. Hosts and PSVR users do not have this issue.
    • STATUS: The player that's in party chat just needs to go into their PS4 party settings and change the voice priority from party chat to in-game chat. That allows the game to receive the voice data and the player can then pass the mic check.


    ENTERPRISE 1701-D-SPECIFIC


    • NAME: Transporter UI Doesn't Respond (1701-D Bridge)
    • DESCRIPTION: When playing on the 1701-D bridge with a human player manning the Ops panel, it is possible to get the UI panel in a state where the transporter functions no longer accept input. The following steps can cause this to occur:
      1. Have (at least) 1 crew member assigned to the Transporter Bay in the Crew Management panel.
      2. Obtain a Transporter target lock (# of targets to be transported does not matter).
      3. Select Energize.
      4. Quickly go to the Crew Management panel and deactivate the crew member assigned to the Transporter Room.

    Following these steps, if the timing is quick enough, this issue can render the entire Transporter side of the Ops panel inoperable.

    • HOW TO AVOID: When transporting targets, avoid changing crew assignments in the Transporter Room until the transport is complete.
    • WORKAROUND: This bug does not occur if an AI crewmember is manning the Ops panel. In a game with 3 or fewer players, have the human player manning Ops move to another station so the AI mans the Ops panel - this will correct the issue. In a 4 player game (no AI crew), it is not necessary to abort the mission, instead you can have the human player manning the Ops station drop from the session and then rejoin to correct the issue.




    AEGIS-SPECIFIC

    FIXED

    • NAME: Missing system intrusion SFX
    • DESCRIPTION: Clients do not generate SFX for system intruding while intruding
    • STATUS: Fix ready for next patch

    NO FIX - Performance load is too great for minimum system specs to allow exact screen replication - blank panels were added so the Captain isn't just pushing buttons in the air.

    • NAME: Empty holo screens
    • DESCRIPTION: Captain's chair holographic screens are empty from other stations
    • STATUS: Bug recreated by QA, under investigation



    ORIGINAL ENTERPRISE-SPECIFIC

    FIXED

    • NAME: Hidden subsystems
    • DESCRIPTION: Repair view panel does not show Subsystem for non-Engineer Stations
    • STATUS: Bug recreated by QA, under investigation

    NO FIX - Code dependencies make the fix risk too great - could open up new bugs. That means the Tactical Station has an exclusive, but accurate, view of charge levels and crews should coordinate accordingly in this regard. Communication is key, Officers!

    • NAME: Obscured Phaser charge
    • DESCRIPTION: Tactical Screen not showing Phaser charge levels
    • STATUS: Bug recreated by QA, under investigation


    FIXED

    • NAME: Engineering AI ‘reset’
    • DESCRIPTION: Repair crews assigned by Host in engineering station are being moved to unassigned once host leaves engineering station
    • STATUS: Bug recreated by QA, under investigation


    FIXED

    • NAME: AWOL repair crews
    • DESCRIPTION: Client assigned repair crews are invisible upon returning to engineering station.
    • STATUS: Bug recreated by QA, under investigation


    FIXED

    • NAME: Double scanning
    • DESCRIPTION: Captain on the Enterprise (TOS) is able to use the onscreen commands hologram and the Padd to scan targets independent of tactical
    • STATUS: Could not reproduce this exact behavior after extensive QA hours. We did find a bug to enter that may be the closest to this and have added it for investigation: “Scan command from Analyze Target crewbot order continues if tactical seat becomes occupied”

    Share this post

  2. #2
    Thanks UbiDomZ! It's great to get a status update for these and to know that the team is investigating. I look forward to seeing the updates as each of the bugs makes it into JIRA and through the replication, and hopefully fix, processes. This is really reassuring, thank you for keeping the community informed.
    Share this post

  3. #3
    Thank you UbiDomZ! Fantastic to see this kind of awareness/communication. Really makes a huge difference to those of us who are most passionate about the game. Hoping to see more of the bugs logged by Cpt Summers being addressed.
    Share this post

  4. #4
    UbiDomZ's Avatar Community Manager
    Join Date
    Aug 2017
    Posts
    555
    Thanks for sharing your thoughts! Keep an eye on this thread, as we'll be updating it with new information periodically (like today!) The team truly appreciates all of your feedback and suggestions, so keep them coming.
    Share this post

  5. #5
    Update today? With the game patch or more info with a future patch goal info,date.
    Share this post

  6. #6

    Watson not functional on Enterprise D

    Thank you UbiDomz for the update on the game. In this thread I saw bugs regarding the original enterprise and general gameplay. However I do not see any bugs regarding the Enterprise D on PS4. One standout annoying bug is one for Watson not working for single player voice commands. In not sure if you were aware of this but if not than here it is. Thank you for your time.
    Share this post

  7. #7
    That's a known issue. They have to update their Watson integration with the TNG commands, and just haven't released the patch yet. Definitely coming though.
    Share this post

  8. #8

    TNG Enterprise D Updates?

    Thanks for the updates!

    Wondering about acknowledged bugs and upcoming fixes for the TNG DLC. The one that's bugging me the most is the transporter bug when you have a human crew. Being unable to transport during the Borg mission causes mission failure. (I do understand that it can still be completed by AI but defeats the purpose of having a human crew)

    Again, thanks for keeping us up to date, and looking forward to the next patch.
    Share this post

  9. #9
    Appreciate the updated info. I'm a little concerned though. Does this mean that the transporter bug isn't scheduled to be fixed at all?

    As specific as those steps make it sound, people are running into this issue all the time, probably because reassigning crews from the transporter room after a transport is EXACTLY what you'd want to do. Having to drop and rejoin a game to fix it is a pretty game breaking workaround, especially in an intense mission like the borg.
    Share this post

  10. #10

    Fix the missing decals on Enterprise D?

    Did you fix the missing hyphens on the Enterprise D? Remember it's NCC-1701-D. NOT NCC 1701-D
    Share this post