CCP_Darwin

CCP_Darwin



25 Nov

Comment

Glad your issue is fixed! Just a note: bug reports don’t usually get an individual response unless we need more information. If you need individual assistance, you should open a support ticket. It’s appropriate to open both if necessary.


20 Nov

Comment

It also occurs to me that this sounds like it might be a problem with the GPU drawing too much power. If that were an issue, you might find it helps to make sure (if not already the case) that you have Interval One set in your graphics settings.

Comment

If you can do it in game, great, if it just can’t happen, I understand! Please feel free to put my name in the bug report so it’s directed to me and I’ll pass it to the right people.

Comment

Don’t worry about whether you think the right data will be submitted. Just please submit an in-game bug report after this happens. 10 minutes to recover and relaunch the game should be no problem at all. We get a lot of data with such a submission and it’s all a lot more helpful than discussing it here.

If you absolutely cannot submit a bug report in-game, the alternative procedure I wrote up above is an alternative that would still help quite a bit.


11 Nov

Comment

For your case, if you have trouble using the in-game bug reporter, I suggest:

  1. Try to take a screenshot of the broken Eve session. On Windows 10, Windows-shift-S will let you do this. If you’re on a Mac, you can try command-shift-3.

  2. If you’re on Windows, run dxdiag and save the output. If you’re on the Mac, you can do the same thing with System Profiler. Instructions for both are here:

Read more

10 Nov

Comment

Here’s what I’d suggest doing: Next time you have the problem (or next time you can induce the problem) go ahead and let the monitor go to sleep. Restart, then open Eve and immediately file an in-game bug report. We might be able to see the logging from your previous session with your report, but even if not, the hardware and software rundown of your machine will be super-helpful in tracking this down.

Also, it’s possible that different power settings or even a different monitor cable may solve this. If you search “monitor sleeps randomly” on Google, you’ll find various sites with instructions on how to adjust the power settings. I’m hesitant to link one directly because I’m not sure which advice is most accurate or comprehensive. (Even if you’re only seeing this problem in Eve, it could be something like an interaction between your power settings and what Eve is doing, so this might be a useful workaround.)


09 Nov

Comment

@DeMichael_Crimson @Jinx_De_Caire

First, I’d strongly recommend double-checking that you’re on the most recent graphics drivers for your systems. Out of date drivers can cause problems if we make changes that depend on manufacturers’ fixes you might have missed.

Second, for issues like this, it’s extremely helpful if you could submit an in-game bug report. If your issues are specific to your hardware or software configuration (and for this issue it looks like that may be the case) the in-game bug report tool sends us a package of information that can help us track that d...

Read more

28 Sep

Comment

Hi! Sorry for the delay responding to this.

This was not the intended behavior for this item, and it’s been fixed as of today’s patch. Hope that helps.

Patch notes for version 19.08, released 28 September 2021


05 Oct

Comment

We still construct and update the space scene with this mode enabled. This enables toggling the mode instantly, but means you don’t get any VRAM savings.

Comment

Unfortunately not. There was concern raised that players might enable this mode by mistake and would need help getting out.

Comment

Can you set your settings back and submit an in-game bug report? Would be interested to see what your hardware/driver/settings situation looked like.


02 Oct

Comment

Try setting your Interval to Interval One. Otherwise, Eve will crank out all the frames it can, to the limit of your CPU and GPU.

Comment

It’s possible these could be represented in tactical view in the future, but in the meantime, simply toggling on 3D graphics to see the bubbles will likely be your best bet.

Comment

As you probably know, we used to have a setting that replaced the 3D view in hangars with a still image. It was removed as part of a pass to simplify the settings menu by taking out lesser-used settings.

Not sure if bringing that setting back would be on the table, but in the meantime I suggest binding this toggle to a convenient key and toggling when you dock or undock. It takes effect instantly and you will probably forget you’re doing it.

Comment

We’re hoping this will be useful both for players who want to lower GPU load on very low-end machines and for those who are engaged in fleet fights with thousands of players on grid that might be very taxing for their systems to render.

Comment

That’s not a bad idea. I’ll pass it on to the appropriate people on the graphics team.


22 Apr

Comment

Whomever. (Sorry, just trying to get into the spirit of this thread.)


18 Apr

Comment

Thanks for the detailed feedback. I’ll make sure this gets back to the right people! We do a lot of targeted outreach toward new players, but not everyone hears from us, and I’m very sorry you didn’t.

In any case, please keep posting your thoughts on the forums and even if we don’t always respond, we’ll be here to see it.


16 Feb

Comment

If you can submit a bug report in-game, that would be hugely helpful for tracking this down. Doing so sends us a package of information about your system that includes details about your sound hardware and drivers that might matter.

Press F12 and choose Report Bug once you’re in the game.


11 Feb

Comment

We do not guarantee a response to bug reports. Generally, you should use a bug report when you are telling us about a bug (as you did) but not when you require a response, such as if you need assistance with your account. In this instance, the problem you reported is a known issue, and we track those using a different system than the one used for bug reports, so your bug report was closed.