![]() ![]() Still playable against predictable NPCs, but only barely. Any sort of “fog” effect, like in an asteroid belt or some combat anomalies, will bring the framerate crashing down into the single digits.Warping, gate animations etc were still much smoother than under WINE. But the framerate was still pretty decent. This is far from optimal on such old hardware, so I never expected top (or even good) performance. I then took a few combat trips with different settings. confirming the “client closed unexpectedly” error upon quitting, just for the record.The mouse scroll button is rather sensitive - zooming in and out is basically toggling between “a galaxy far, far away” or “right up your ass” (mouse: Logitech MX Master 2S).Player and NPC portraits don’t seem to load?.DoD seems to have skipped some things, I still got short delays and temporary low-poly models when undocking.(specs: MacBook Pro (Retina, 15-inch, Mid 2015) - Technical Specifications)įullscreen mode, Dell U2711 2560x1440 27" monitor – haven’t yet played on a retina screen Playing on a 2015 MBP running macOS 10.15.7. I’ve read, and re-read this reply - the playtest ends on April 21st, that’s 5 days time - I don’t see any assurance that, on that day, my Eve days will not, in an instant, be over. ![]() I’m also NOT asking for a 32-bit version - the OS has been 64-bit since 10.7 (I simply don’t understand the statement quoted above) - to be sure my 10.13.6 is 64 bit (“getconf LONG_BIT”) …all macOS versions before 10.15 are 32-bit I’m happy not to be running the test software, and to not have access to Sisi. Although your reply leaves me somewhat confused. That may change, but it’s hard to predict business decisions around ROI for continued maintenance of deprecated systems. CCP is going to try to make it happen, but the solution may not be within the native Mac client, and they aren’t promising continuing to support the WINE launcher afterward right now. The native client has been written for 64-bit systems, so adding backwards compatibility with 32-bit systems is a challenge, and all macOS versions before 10.15 are 32-bit. Off to bed, as I need to go talk to a guy and a gal about buying a house… I will do more testing - video capture - and bug reports tonight/Soon™. Trying to change the resolution did not work, but I was able to click the Green Apple button to full-screen the app which fix the screen resolution, but was unable to get it to go into window mode. Second client booted (probably where most of my heat was coming from), but the screen was massively over res. I ended up finally dragging the window to a bigger res which the client kept. Going slow and finding the point in which the window options would highlight, I was able to change the resolution and got the mouse point to hover correctly. Window mode was possible, but with the first transition to window mode, the mouse pointer was not aligned right. MBP was getting a little warm, but no where nears a warm as with wine client. FPS monitor running and my menu bar shows CPU, GPU, memory %s. The eye candy was taken in window mode (which worked for first client) max settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |