These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Macintosh

 
  • Topic is locked indefinitely.
 

Cannot See Probes in Space...

First post
Author
Previous Topic Next Topic
Ragashingo
Elixir Aeutet Corporation
#41 - 2013-06-10 03:17:30 UTC
Strange indeed. I just had it working, restarted without touching anything, and it was broken again. I'd try and reproduce it working / not working but I have no idea what could have changed in the minute it took to restart the game…
Ander Fred
Aliastra
Gallente Federation
#42 - 2013-06-10 13:10:49 UTC
Confirmed as NOT a graphics driver glitch. The issue APPEARS to be with the presets. It was the 'launch pinpoint' button that caused it on mine during an experimental session, but ONLY after a certain set of circumstances, the likes of which I'll be trying to reproduce now. Wall Of Text to come.
Ander Fred
Aliastra
Gallente Federation
#43 - 2013-06-10 13:28:56 UTC
Fitted Core Probe Launcher I to Helios, 8 core probes
Undocked
Jumped to Muvolailen
Wait for system scan to finish
Break cloak and move
Bring up DScan
Switch to probe scan
No sigs to scan, so move to Annaro
Sigs in Annaro, DScan has not been closed
Break cloak
Launch probes
F10 to map view, it's in star view, switch to solar
Probes are showing
Minimise map control
Scale probes in, press scan
Change to poinpoint formation, move map view, move probes to be over the point
Scan
Adjust viewpoint, position, scale probes by dragging the sphere
Scan
Move probes, adjust view. Scale stays the same (I changed targets)
Adjust viewpoint, position, scale probes by the Probe Scanner interface (0.5AU)
Scan
Result locked. Recall probes by clicking recover in the interface. Ctrl-R to reload.
Launch probes again. They show as being in the exact same place they were when I recalled them.
Press scan, they warp to and scan.
Recall and reload probes
Warp to station and dock
Undock
Launch probes, they again assume the position and scale they were last in
Recall probes, crtl-r to reload, warp to next gate (Isutka)
Wait for system scan. Sigs found.
Decloak by speeding up (map is still open in solar view) and launch probes. Probes show fine
They've launched in pinpoint format, same scale as before, not sure of same position. Will have to try and find a way to test this.
Move, rescale, adjust viewpoint
Scan
Repeat till lock, all found, all fine. Time to play with buttons
Click 'launch in spread formation' Works fine
Spam between spread and pinpoint, works fine
Resize ONE probe to max and drag it out of formation
---Lost connection here---
Press Esc->logoff. EVE has now gone spastic and is replicating, so close all instances of EVE (including 2nd client, made using clonemaker)
2nd doesn't want to quit and has to be crashed.
Launch just the testing account. Takes a bit longer than usual but fires up fine. Log in and enter as test character.
DScan is still up, reconnect to probes. F10 to map, all probes are now 32 AU and maladjusted (PIC: ET1)
Press scan, works fine
Press 'pinpoint formation': ERROR! Bug produced.
Exit map view
Recall probes
Click launch spread
Load probes by right click (since crash removed the ability to reload)
Press Launch pinpoint, error still present
Press launch spread, error still present
Recover probes.
Log off.
Log in, select different toon on same account
Undock, jump to Osmon from Jita to pick up the frig. Noticed a combat site in Jita...
Dock up in Osmon, switch to ship. Expanded launcher and core probes. Undock.
Click probes to launch, F10 for map view. Bring up Dscan. Error is present. No further testing possible.


Things to note: 2 clients running via the clonemaker. Client 2 had the bug first, but client 1 was unaffected. However, characters on the same account share the bug. This should hopefully narrow things down. My first guess here would be looking at where the probe location info to keep them in the same place/size is stored. I'll try some file deleting and see where it gets me.
Ander Fred
Aliastra
Gallente Federation
#44 - 2013-06-10 14:36:48 UTC
Can confirm cache manipulation removes the error. Will work on exactly what tomorrow. Bug report filed pointing to the post.
Snuskpelle
Snusk Inc.
#45 - 2013-06-10 15:26:21 UTC
why are we even posting here.. the Dev's have abandoned this thread. fixing career starter missions has priority. Ugh
Ammathi
Warteck Trading Co.
#46 - 2013-06-10 18:46:08 UTC
Just another bump on this, same issues as described above, sometimes they work, sometimes not, thanks for all who are trying to pinpoint this.
Vincent Athena
Photosynth
#47 - 2013-06-10 23:07:29 UTC
Does anyone using 10.7.x or less have this problem? Or is it limited to 10.8.x?

Know a Frozen fan? Check this out

Frozen fanfiction
Ander Fred
Aliastra
Gallente Federation
#48 - 2013-06-11 00:04:50 UTC
Ander Fred wrote:
Can confirm cache manipulation removes the error. Will work on exactly what tomorrow. Bug report filed pointing to the post.


Ok scrap that. Must have been something else, cos no matter what I do now I can't remove this bug. Wiped cache, new clones, still same problem. Without a way to reverse this I can't do any more work on producing it. One question though, did anyone have the bug FROM LAUNCH. As in the very first time they scanned, it was ALREADY bugged?
Fallax Nexhawk
Center for Advanced Studies
Gallente Federation
#49 - 2013-06-11 01:41:28 UTC
Ander Fred wrote:
Ander Fred wrote:
Can confirm cache manipulation removes the error. Will work on exactly what tomorrow. Bug report filed pointing to the post.


Ok scrap that. Must have been something else, cos no matter what I do now I can't remove this bug. Wiped cache, new clones, still same problem. Without a way to reverse this I can't do any more work on producing it. One question though, did anyone have the bug FROM LAUNCH. As in the very first time they scanned, it was ALREADY bugged?


Strangely enough, I didn't have this problem on the 5th, when I first played EVE after Odyssey deployment. On the next day, however, my probe spheres have disappeared and haven't appeared ever since.
Ammathi
Warteck Trading Co.
#50 - 2013-06-11 03:28:47 UTC
confirmed day 1 issues here. loaded odyssey and had the issue, first thing i did when i logged was try to scan the new sites, leading to this forum post :(
giles666
Red Phoenix Rising
#51 - 2013-06-11 13:02:39 UTC
Ander Fred wrote:
Ander Fred wrote:
Can confirm cache manipulation removes the error. Will work on exactly what tomorrow. Bug report filed pointing to the post.


Ok scrap that. Must have been something else, cos no matter what I do now I can't remove this bug. Wiped cache, new clones, still same problem. Without a way to reverse this I can't do any more work on producing it. One question though, did anyone have the bug FROM LAUNCH. As in the very first time they scanned, it was ALREADY bugged?


I had the bug day one, however since then it has been intermittently on and off with probes not working about 75% of the time.

I haven't yet been able to work out what causes it to work or not. As far as I can tell it is completely random.
r1kk1
Caldari Provisions
Caldari State
#52 - 2013-06-12 08:35:38 UTC
+1 here too

MacBook Pro
15-inch, Mid 2010
Processor 2.66 GHz Intel Core i7
Memory 4 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GT 330M 512 MB
Software OS X 10.8.3 (12D78)

again seems intermittent, was working before and comes and goes. get that fraction of a second of them drawn properly and then gone again.
Laris Orwan
DigiLab
#53 - 2013-06-12 20:29:55 UTC
Same problem for me... MacBook but I'm still on 10.8.3!!

Come one CCP this isn't fair on us mac guys is it?

:(
Ammathi
Warteck Trading Co.
#54 - 2013-06-13 06:23:10 UTC
Still no update?.. Please give us something devs, this is quite a frustrating bug to have going on with the expansion that is all about exploration.
Ander Fred
Aliastra
Gallente Federation
#55 - 2013-06-13 08:12:09 UTC
Well what we *can* say for sure is that the probes do draw for a fraction of a second when you press the scan button. So that gives the devs a place to start looking. That coupled with my finding on the probe position button may help.
r1kk1
Caldari Provisions
Caldari State
#56 - 2013-06-13 20:56:40 UTC
r1kk1 wrote:
+1 here too

MacBook Pro
15-inch, Mid 2010
Processor 2.66 GHz Intel Core i7
Memory 4 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GT 330M 512 MB
Software OS X 10.8.3 (12D78)

again seems intermittent, was working before and comes and goes. get that fraction of a second of them drawn properly and then gone again.


interestingly, i just installed 10.9 to test and it doesn't seem to be present there on the same machine.
Ander Fred
Aliastra
Gallente Federation
#57 - 2013-06-14 01:47:11 UTC
Can you make it happen though?
Zeus Zed
Federal Navy Academy
Gallente Federation
#58 - 2013-06-15 20:40:28 UTC
I too have the same problem on my mac pro 10.8.4 NVIDIA 285GTX

Never experienced anything like that before Odyssey, so it's a ****-up from CCP's side.

Please fix it asap - exploration is THE thing for Odyssey and we can't play.
Spacemover
The Scope
Gallente Federation
#59 - 2013-06-17 20:02:54 UTC  |  Edited by: Spacemover
worked fine yesterday, is not working today...

ingamesettings
https://docs.google.com/file/d/0B16KO9JjfSbnQlp4c1o4XzBob1U/edit?usp=sharing

mac book information
https://docs.google.com/file/d/0B16KO9JjfSbnOVdWX2dBaXZWZGs/edit?usp=sharing

tried clear cache stuff, mac client repair, graphicsettingsfaceroll, nothing is working.
Hjordis Bjorklund
The Scope
Gallente Federation
#60 - 2013-06-17 22:38:32 UTC
Getting OSX 10.9 this week to test with and come on CCP. Why isn't this getting awareness? At least give us an update. It's been two weeks already. It's game breaking!