Right out the gate - this is not the place to complain about how the IC works. I will do my best to explain how the IC actually works, and how to better use the system we have. Leave feedback where CIG will actually see it. If you have questions, suggestions, or things I missed please add them below! Last Updated 23 NOV 2024 TLDR - What The IC is for and What it isn't The IC is not for feedback. Your frustrations or feelings about an issue do not belong on the IC, they belong on the feedback forums. The IC is not a place to request help, test chat, helpdesk, and the technical support forums are all excellent resources for that. The IC is for issues. Bugs, error codes, crashes and general wonkiness all belong on the IC. If you're not sure if a thing is a bug, lack of feature, or feedback, ASK! Test chat is an excellent resource usually filled with experienced testers who are willing to help you. Test Chat - https://robertsspaceindustries.com/spectrum/community/SC/lobby/38230 [discussing bugs, testing, and active builds, up to date info from staff] Helpdesk - https://robertsspaceindustries.com/spectrum/community/SC/lobby/7 [for more technical help, no staff here, only volunteer backers] Feedback - https://robertsspaceindustries.com/spectrum/community/SC/forum/4 [for your thoughts, feelings, emotions, and ideas on everything SC] Focus Test - https://robertsspaceindustries.com/spectrum/community/SC/forum/190049 [test announcements, regression, bug discussions] PART 1 - Existing Resources IC Forums https://robertsspaceindustries.com/spectrum/community/SC/forum/260633 Official communications about the IC platform and how to use it Searching the Issue Council https://support.robertsspaceindustries.com/hc/en-us/articles/22529807104279-Searching-the-Issue-Council A full guide to using search operators. I will reference this constantly and use them extensively, please read (or skim) this. General IC use guide https://support.robertsspaceindustries.com/hc/en-us/articles/115009643527-Bug-Reports-Using-the-Issue-Counci CIGs official guide. I will not be covering basic functions, CIG did a phenomenal job of that already. Severity guide: https://support.robertsspaceindustries.com/hc/en-us/articles/115009643527-Bug-Reports-Using-the-Issue-Council#h_01F3R2R95Z759MC55V44T28DF0 This section specifically talks about severity. Your own feelings about the bug do not matter, leave your feelings on the feedback forums. Please follow this guide for severity, as it makes the job of others much easier if you do. Most Recent CIG QA Communication About the IC https://robertsspaceindustries.com/spectrum/community/SC/forum/260633/thread/addressing-issue-council-communications/426328 CIG QA describing some of the issues they see with the IC, and clarifying some misconceptions about the platform. There are two sections on the IC, one is for reporting bugs with the game, and the other is for reporting bugs with the launcher. Once you are at the main menu, the error should go on the Star Citizen IC, this includes any CTD. Anything that occurs before you get into the game should go on the Launcher side. To get started, click the link below. https://issue-council.robertsspaceindustries.com/ PART 2 - Before you even go to the IC Always turn on r_displaysessioninfo 1 at a minimum, this turns on the QR code with session data. Turning on r_displayinfo 2 (3 is more helpful, but 2 is fine) is also helpful. Always submit screenshots and/or video with the session code. This is very helpful to both other testers trying to reproduce (repro) your issue as well as CIG internally. If you are getting a specific error code (such as 60016, or 30018) submit your logs! These logs will be locked so that only CIG and you can see them, so you don't need to worry about data being shared with other backers. https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues/STARC-135826 PART 3 - Finding and adding to existing tickets This is the most common thing you will do. Very often you will find that someone else has already reported your issue. BEFORE YOU CLICK 'REPORT A NEW ISSUE' Read the search guide linked above Search using the search bar [https://issue-council.robertsspaceindustries.com/projects/STAR-CITIZEN/issues] Use the filters to narrow results. Change your search terms, be inventive. If you get more than one or two pages your search-fu needs some work. Try and try again to narrow relevant results. Ask in test chat if anyone has a ticket Search AGAIN, think real hard Actually read the tickets that come up Wildcards [*] can actually prevent appropriate tickets from showing in the search results. When changing search terms, you need to erase the entire string and start over or IC will often only account for the change. For example, if you write [salvage + disappear] and then change it to [salvage + disappear | vanish] the IC may only search for 'vanish' and ignore the other terms. DETERMINING WHICH TICKET TO ADD TO (There's so many! Which is the original!!!!) In general, try to respect the 'oldest ticket first', but this requires a little bit of experience and objectivity. If a newer ticket is better written, it may be better to contribute to the 'better' ticket. Use your judgement, it's something you'll learn over time. ACTUALLY ADDING STUFF Follow the severity guide! The original writer of the ticket may not have followed the guide, but you should where possible. There's a degree of subjectivity here, so don't be a pedant either! Example - The Zeus being unable to enter NAV mode at all is still only 'Hardly Playable' as it severely hampers gameplay but does not prevent it entirely. If the Zeus cannot power ON at all, that now becomes a 'Critical' bug as it cannot take off at all. If you need to upload logs, do it on the 'Game Version' tab Always add evidence when possible! More evidence (with session code) helps CIG track down the issue faster. Screenshots are great, video is better. Adding comments is a best practice, but not always required. If you have nothing new to add and are just confirming an issue, they are not necessary. If you do have something new to add, add it! You can always edit your post after you submit it. It is also best practice while a ticket is still open between versions to go back and check if an issue still exists. If it does, update the version on your contribution by editing it! This really helps QA to prioritize. Sometimes the only way they have of tracking how bad an issue is, is the number of recent contributions. Because I hit the character limit: PART 4 - WRITING A BETTER TICKET https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/the-issue-council-and-you/7370971 PART 5 - ARCHIVING AND FIXED STATUS https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/the-issue-council-and-you/7370973 PART 6 - EXAMPLE TICKETS https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/the-issue-council-and-you/7370995