Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.95a is out! (03/26/21); Blog post: Of Slipstreams and Sensor Ghosts (09/24/21)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Adje

Pages: [1]
1
Well, it seems to be working again doing both the suggestions of what Histidine and Alex said, but then reverting back to my own settings, to test to see if the changes actually worked, also doesn't give me the bug anymore. I've done nothing else in between applying the suggestions and my initial post. I'll see later on if the bug happens again, since it's been happening for about two weeks now, then apply the suggestions and see if they get results.

2
When launching Starsector, my computer initially freezes for about half a second, then in about 2 seconds, slows down to a crawl where it looks like the PC runs at 1 frame every 4-5 seconds, and input from the keyboard/mouse is also significantly delayed. If I close the initial screen to launch starsector, the screen freezes to the image of my desktop. Navigating anything becomes impossible, and launching other programs only creates highly distorted static/pixelation. Shutting it down only produces a temporary black screen, then reverts back to the desktop image until it shuts down. If I launch the game, the game will take ~8 minutes to load, with the framerate issues still occurring, though ending the java process while the game loads or has loaded to the main menu causes no errors, and the PC operates normally.

So far, I've tried a number of things, such as:
Updating GPU drivers
Turning off all non-essential services/programs, except those to run Starsector
Install and launch the game from a different storage device
Using a different, known good GPU (GTX 1060 6GB)
Adjusting resolution/refresh rate using both GPU's

So far, nothing I have tried has made any difference, same bug happens every time.

SPECS:
OS: Windows 7 Professional 64-bit SP1
CPU: Ryzen 2600x
MB: ASUS PRIME X470-PRO
RAM: DDR4 16 GB 3200MHz
GPU: NVIDIA GeForce GTX 970
STORAGE: Samsung SSD 860 EVO

So far, I have only been able to play with this new setup once late at night, and I'm not even sure how/why it was able too, just that I could for the time being until I closed the game. This was with version .9 RC8, if that means anything. No other version I've tried so far has worked, even repeated attempts on .9 RC8.
This bug has not occurred when I was playing the game on a different setup.
This same bug also happens when I attempt to play Zero-k on steam, if this tidbit means anything. No other games I have played, so far, has caused this issue.

3
Bug Reports & Support (modded) / Guaranteed Gamma AI Core Drop
« on: September 07, 2017, 11:00:00 PM »
Spoiler
[close]
Spoiler
[close]
Spoiler
[close]

After attacking the rems and allowing all but one to retreat, letting them go after the initial engagement (or being above a debris field?) guarantees a single gamma ai core drop.
I'm not sure if its a specific mod causing this or a base game issue, but I posted it here because I have no clue.

About to test and see if another group I haven't attacked yet causes this.

EDIT:
Spoiler
[close]
Spoiler
[close]

Same results with another group I haven't touched yet, not above a debris field.

4
Mods / Re: [0.8.1a] Diable Avionics 1.86 (31/07/2017)
« on: August 15, 2017, 08:46:09 PM »
For NoScript, you should see something pop up that says it filtered a cross-site scripting (XSS) attempt. To the right of that message should be an options menu, you'll want to click unsafe reload and click yes.
Picture provided.


Pages: [1]