Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

580X Vs Vega 48 in the real world?

bondavi said:
Unboxed my i9 and ran benchmarks, also my old 2017.

2017: i5 3.8 32GB, 2TB Fusion, Radeon 580
2019: i9 3.6 40GB, 512 SSD, Radeon 580X

Geekbench:
2017: 5136/16587
2019: 6366/34308
OpenCL Score: 119722/118202

Heaven Benchmark:
See below.

Have only had system powered up for 20 minutes. But basically same GPU performance.
Click to expand...

Heaven is an older benchmark from 2009. Yes, it's still pretty demanding on certain video cards, but I'm not sure that it's terribly relevant for recent games. It's essentially a tessellation demo. The "benchmarking scene" (e.g Jays2Centz) tends to use Battlefield V, Timespy, and sometimes that recent Tomb Raider. Of course, they're messing about with ray tracing-- which is mostly associated with nvidia's 2070, 2080, and 2080ti and not AMD.


More to the point, if you are interested in gaming, you wouldn't use 1600x900. An Imac gamer would prefer 2560x1440 or 5280x2880 (for older games). And those resolutions might show a difference.

Now, if I was in the market for an iMac (my current machine, though out of warrenty, still has plenty of life in it), I'd be interested in
  1. What new things can I do with the new machine? Does the Vega chip drastically improve machine learning performance?
  2. Can I play my existing games at a higher resolution or better graphics quality (Of course, right now, I'm playing FTL, which doesn't really use the gpu. But I had a Surviving Mars campaign which sometimes stuttered at 2560x1440.)
  3. I have a projects which involves scanning old historical documents and running OCR on the results. The process can take hours-- possibly because Finereader's image preprocessor isn't well optimized. I imagine that at least a few computer users have similarly complex tasks, and would like to see an hour's task shaved down to half an hour or less. A benchmark that takes hours to run may not be convenient, but it's hugely valuable.
So, if I had an imac 2019 for testing purposes, I'd try to do stuff that's not possible on an older machine.

Can I play this game at this resolution, but now at 60 frames a second?
Can I play this game at this resolution, but now at "Ultra detail"? (and is this difference perceptible?)
Can I complete this task in less than n hours? Will my work-life involve less "coffee breaks"?
Is this sort of editing possible in real time (without rendering at fractional resolutions)?


That sort of information is more valuable than "overall, five to ten percent faster".

Think of battery life in laptops. There's a certain threshold, once past, lets the user leave the bulky, heavy power supply at home. It doesn't really matter that the battery life is only fifteen percent lengthier than last year's, it matters that the battery life, as realistically measured, exceeds the number of minutes that the user regularly spends away from home.
 
Last edited:
  • Like
Reactions: auduchinok, InformationLandmine and Colonel Blimp
bondavi said:
Have only had system powered up for 20 minutes. But basically same GPU performance.
Click to expand...

Thanks for posting this! I find it a bit strange that the 2019 iMac even is a little bit slower than the 2017 one, would've expected an 8-10% higher score due to the 580X running 100MHz faster than the 580 if I'm not mistaken. I'd suspect that the system was busy in the background, indexing files and such, as you had it running for only 20 minutes. Of course, I'm not sure how much that affects a GPU benchmark.

Good to hear the system is running cooler than the 2017 one, though. :)

Could you maybe repeat the Heaven benchmark after your iMac has been running for a couple of hours, just to check if the value increases? Would be much appreciated-thanks!
 
Here you go, after 3 hour burn in, then restart. Slight bump.

I'll install Windows next.
 

Attachments

  • Screen Shot 2019-04-11 at 4.38.04 PM.png
    Screen Shot 2019-04-11 at 4.38.04 PM.png
    123.9 KB · Views: 566
  • Like
Reactions: rxs0 and Bohemien
Cashmonee said:
To be clear, while the Vega 64 is not too far behind the RTX 2080Ti in the test you link to, the two cards are not in the same league overall. The 2080Ti is a far better and more capable card. The Vega 64 competes more closely with a vanilla GTX 1080 or RTX 2070.
Click to expand...
It really depends on what you need. If you only look at gaming, yes they aren’t close. But if you look at compute benchmarks (like that Lightroom benchmark) things can look a bit different. If you have software that is heavily compute based and doesn’t use CUDA, people can be better off with AMD. I believe macOS leverages the compute strengths of AMD hardware.
 
  • Like
Reactions: throAU and jerwin
My 2019 iMac with Vega 48 arrived yesterday. I had hoped to post some benchmarks here, but Unigine Heaven 4.0 and Valley 1.0 (the current versions) are both crashing immediately upon launch, upon both my iMacs (2015 and 2019) running macOS 10.14.4.

My 2015 iMac used to be able to run these, and other folks seem to be posting Unigine benchmark results, so what’s going on? I searched Google, DuckDuckGo, and the MacRumors Forums and found nothing similar.

It’s not a hardware problem, since it affects both my 2015 iMac with M395X and my 2019 iMac with Vega 48.

It might be an incompatibility with macOS 10.14.4 (the 2015 iMac is running build 18E226 and the 2019 iMac shipped with build 18E2034), although that seems unlikely. (Are you all able to run Heaven and Valley in macOS 10.14.4?) Or it might be some strange software incompatibility on my iMacs, as I migrated my apps and settings from the 2015 to the 2019 iMac via Migration Assistant.

Here’s a typical crash report. Heaven or Valley, 2015 or 2019 iMac, it’s always the browser_x64.macos process that crashes in thread 0 with segmentation fault 11. Can any of you make sense of this?

Process: browser_x64.macos [2886]
Path: /Applications/Heaven.app/Contents/MacOS/./browser_x64.macos
Identifier: com.Unigine.Heaven
Version: 4.0
Code Type: X86-64 (Native)
Parent Process: ??? [2884]
Responsible: browser_x64.macos [2886]
User ID: 501

Date/Time: 2019-04-11 22:27:39.311 -0700
OS Version: Mac OS X 10.14.4 (18E2034)
Report Version: 12
Anonymous UUID: [Redacted]


Time Awake Since Boot: 15000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.qtkit64.server

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2886]

VM Regions Near 0:
-->
__TEXT 0000000100000000-000000010000c000 [ 48K] r-x/rwx SM=COW /Applications/Heaven.app/Contents/MacOS/browser_x64.macos

Thread 0 Crashed:: Dispatch queue: com.apple.qtkit64.server
0 com.apple.CoreFoundation 0x00007fff4050a60b CFStringGetCString + 43
1 com.apple.QTKit 0x00007fff4a5ce542 __51-[QTKitServerController startUsingServerForObject:]_block_invoke + 1238
2 libdispatch.dylib 0x00007fff6c90d63d _dispatch_client_callout + 8
3 libdispatch.dylib 0x00007fff6c919129 _dispatch_lane_barrier_sync_invoke_and_complete + 60
4 com.apple.QTKit 0x00007fff4a5cdf7a -[QTKitServerController startUsingServerForObject:] + 179
5 com.apple.QTKit 0x00007fff4a5c435d +[QTMovie_QuickTime movieFileTypes:] + 66
6 libQtWebKitUnigine_x64.4.dylib 0x0000000100375402 WebCore::mimeCommonTypesCache() + 130
7 libQtWebKitUnigine_x64.4.dylib 0x0000000100373d39 WebCore::MediaPlayerPrivateQTKit::supportsType(WTF::String const&, WTF::String const&) + 73
8 libQtWebKitUnigine_x64.4.dylib 0x0000000100a64c71 WebCore::bestMediaEngineForTypeAndCodecs(WTF::String const&, WTF::String const&, WebCore::MediaPlayerFactory*) + 177
9 libQtWebKitUnigine_x64.4.dylib 0x0000000100a64fd8 WebCore::MediaPlayer::supportsType(WebCore::ContentType const&) + 140
10 libQtWebKitUnigine_x64.4.dylib 0x0000000100a5200d WebCore::HTMLMediaElement::canPlayType(WTF::String const&) const + 39
11 libQtWebKitUnigine_x64.4.dylib 0x0000000100126e01 WebCore::jsHTMLMediaElementPrototypeFunctionCanPlayType(JSC::ExecState*) + 257
12 libQtWebKitUnigine_x64.4.dylib 0x0000000100c02765 JSC::Interpreter::privateExecute(JSC::Interpreter::ExecutionFlag, JSC::RegisterFile*, JSC::ExecState*) + 50867
13 libQtWebKitUnigine_x64.4.dylib 0x0000000100c07663 JSC::Interpreter::execute(JSC::EvalExecutable*, JSC::ExecState*, JSC::JSObject*, int, JSC::ScopeChainNode*) + 1377
14 libQtWebKitUnigine_x64.4.dylib 0x0000000100c0707e JSC::Interpreter::callEval(JSC::ExecState*, JSC::RegisterFile*, JSC::Register*, int, int) + 554
15 libQtWebKitUnigine_x64.4.dylib 0x0000000100c0200a JSC::Interpreter::privateExecute(JSC::Interpreter::ExecutionFlag, JSC::RegisterFile*, JSC::ExecState*) + 48984
16 libQtWebKitUnigine_x64.4.dylib 0x0000000100c08414 JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 1268
17 libQtWebKitUnigine_x64.4.dylib 0x0000000100c44121 JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 49
18 libQtWebKitUnigine_x64.4.dylib 0x00000001003bc070 WebCore::JSEventListener::handleEvent(WebCore::ScriptExecutionContext*, WebCore::Event*) + 1140
19 libQtWebKitUnigine_x64.4.dylib 0x0000000100501967 WebCore::EventTarget::fireEventListeners(WebCore::Event*, WebCore::EventTargetData*, WTF::Vector<WebCore::RegisteredEventListener, 1ul>&) + 495
20 libQtWebKitUnigine_x64.4.dylib 0x0000000100501a1b WebCore::EventTarget::fireEventListeners(WebCore::Event*) + 85
21 libQtWebKitUnigine_x64.4.dylib 0x0000000100512d3e WebCore::Node::handleLocalEvents(WebCore::Event*) + 104
22 libQtWebKitUnigine_x64.4.dylib 0x00000001004fc12f WebCore::EventDispatcher::dispatchEvent(WTF::passRefPtr<WebCore::Event>) + 877
23 libQtWebKitUnigine_x64.4.dylib 0x00000001004fab66 WebCore::EventDispatchMediator::dispatchEvent(WebCore::EventDispatcher*) const + 40
24 libQtWebKitUnigine_x64.4.dylib 0x00000001004fb6ec WebCore::EventDispatcher::dispatchEvent(WebCore::Node*, WebCore::EventDispatchMediator const&) + 44
25 libQtWebKitUnigine_x64.4.dylib 0x000000010050e6ab WebCore::Node::dispatchEvent(WTF::passRefPtr<WebCore::Event>) + 51
26 libQtWebKitUnigine_x64.4.dylib 0x00000001004d5950 WebCore::Document::finishedParsing() + 212
27 libQtWebKitUnigine_x64.4.dylib 0x00000001006a4c5f WebCore::HTMLDocumentParser::prepareToStopParsing() + 165
28 libQtWebKitUnigine_x64.4.dylib 0x00000001006a4834 WebCore::HTMLDocumentParser::notifyFinished(WebCore::CachedResource*) + 182
29 libQtWebKitUnigine_x64.4.dylib 0x0000000100732aac WebCore::CachedResource::checkNotify() + 68
30 libQtWebKitUnigine_x64.4.dylib 0x0000000100730d50 WebCore::CachedResourceRequest::didFinishLoading(WebCore::SubresourceLoader*, double) + 150
31 libQtWebKitUnigine_x64.4.dylib 0x00000001007710a0 WebCore::SubresourceLoader::didFinishLoading(double) + 64
32 libQtWebKitUnigine_x64.4.dylib 0x000000010096145d WebCore::QNetworkReplyHandler::finish() + 861
33 libQtWebKitUnigine_x64.4.dylib 0x0000000100961078 WebCore::QNetworkReplyHandlerCallQueue::flush() + 170
34 libQtWebKitUnigine_x64.4.dylib 0x0000000100961cac WebCore::QNetworkReplyWrapper::didReceiveFinished() + 140
35 libQtWebKitUnigine_x64.4.dylib 0x000000010095ef49 WebCore::QNetworkReplyWrapper::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 61
36 libQtCoreUnigine_x64.4.dylib 0x0000000102afd771 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
37 libQtNetworkUnigine_x64.4.dylib 0x0000000102e24aef QNetworkReply::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 59
38 libQtCoreUnigine_x64.4.dylib 0x0000000102afc8e4 QObject::event(QEvent*) + 286
39 libQtGuiUnigine_x64.4.dylib 0x0000000101e636a8 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 304
40 libQtGuiUnigine_x64.4.dylib 0x0000000101e63929 QApplication::notify(QObject*, QEvent*) + 603
41 libQtCoreUnigine_x64.4.dylib 0x0000000102ae8a26 QCoreApplication::notifyInternal(QObject*, QEvent*) + 104
42 libQtCoreUnigine_x64.4.dylib 0x0000000102ae8e13 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 557
43 com.apple.CoreFoundation 0x00007fff40598e88 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
44 com.apple.CoreFoundation 0x00007fff40598dbd __CFRunLoopDoObservers + 451
45 com.apple.CoreFoundation 0x00007fff4053adb4 CFRunLoopRunSpecific + 365
46 com.apple.HIToolbox 0x00007fff3f8279db RunCurrentEventLoopInMode + 292
47 com.apple.HIToolbox 0x00007fff3f82761d ReceiveNextEventCommon + 355
48 com.apple.HIToolbox 0x00007fff3f8274a6 _BlockUntilNextEventMatchingListInModeWithFilter + 64
49 com.apple.AppKit 0x00007fff3dbc1ffb _DPSNextEvent + 965
50 com.apple.AppKit 0x00007fff3dbc0d93 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
51 com.apple.AppKit 0x00007fff3dbbaeb0 -[NSApplication run] + 699
52 libQtGuiUnigine_x64.4.dylib 0x0000000101e24b60 QEventDispatcherMac::processEvents(QFlags<QEventLoop::processEventsFlag>) + 840
53 libQtCoreUnigine_x64.4.dylib 0x0000000102ae5e88 QEventLoop::exec(QFlags<QEventLoop::processEventsFlag>) + 394
54 libQtCoreUnigine_x64.4.dylib 0x0000000102ae915b QCoreApplication::exec() + 175
55 browser_x64.macos 0x0000000100003c9f main + 447
56 browser_x64.macos 0x0000000100003ab4 start + 52

[…]

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000103c397e0 rbx: 0x0000000000000000 rcx: 0x0000000008000100 rdx: 0x00000000000000ff
rdi: 0x0000000000000000 rsi: 0x00007ffeefbfce10 rbp: 0x00007ffeefbfcca0 rsp: 0x00007ffeefbfcc60
r8: 0x0000000000000003 r9: 0x0000000103c91770 r10: 0x0000000000000004 r11: 0x0000000000000004
r12: 0x00000000000000ff r13: 0x0000000102f9bf60 r14: 0x00007ffeefbfce10 r15: 0x0000000008000100
rip: 0x00007fff4050a60b rfl: 0x0000000000010246 cr2: 0x0000000000000000

Logical CPU: 0
Error Code: 0x00000004
Trap Number: 14

[…]

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 8620
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=441.4M resident=0K(0%) swapped_out_or_unallocated=441.4M(100%)
Writable regions: Total=200.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=200.9M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 128K 1
Activity Tracing 256K 1
CG backing stores 1760K 2
CG image 16K 2
CoreImage 32K 3
CoreUI image data 348K 5
CoreUI image file 196K 3
Dispatch continuations 32.0M 1
JS VM register file 4160K 1
Kernel Alloc Once 8K 1
MALLOC 127.8M 40
MALLOC guard page 32K 7
STACK GUARD 56.1M 21
Stack 18.2M 21
VM_ALLOCATE 356K 13
WebAssembly memory 2416K 11
WebKit Malloc 13.3M 9
__DATA 28.7M 291
__FONT_DATA 4K 1
__LINKEDIT 232.7M 9
__TEXT 208.7M 289
__UNICODE 564K 1
mapped file 129.4M 13
shared memory 5412K 11
=========== ======= =======
TOTAL 862.1M 757

Model: iMac19,1, BootROM 220.250.368.0.0, 8 processors, Intel Core i9, 3.6 GHz, 40 GB, SMC 2.46f12
Graphics: kHW_AMDRadeonProVega48Item, Radeon Pro Vega 48, spdisplays_pcie_device, 8 GB
Memory Module: BANK 0/ChannelA-DIMM0, 4 GB, DDR4, 2667 MHz, SK Hynix, HMA851S6CJR6N-VK
Memory Module: BANK 1/ChannelA-DIMM1, 16 GB, DDR4, 2667 MHz, 859B, CT16G4SFD8266.C16FD1
Memory Module: BANK 2/ChannelB-DIMM0, 4 GB, DDR4, 2667 MHz, SK Hynix, HMA851S6CJR6N-VK
Memory Module: BANK 3/ChannelB-DIMM1, 16 GB, DDR4, 2667 MHz, 859B, CT16G4SFD8266.C16FD1
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Feb 21 2019 21:04:15 version 9.137.3.0.32.6.29 FWID 01-d837a364
Bluetooth: Version 6.0.11f4, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi 2, AirPort, en1
Network Service: Ethernet, Ethernet, en0
PCI Card: pci1b21,625, AHCI Controller, Thunderbolt@134,0,0
Serial ATA Device: APPLE HDD ST3000DM001, 3 TB
USB Device: USB 3.1 Bus
USB Device: Back-UPS ES 750G FW:908.W3 .D USB FW:W3
USB Device: FaceTime HD Camera (Built-in)
USB Device: ML-1630 Series
USB Device: Razer Taipan
USB Device: Sennheiser USB Headset
Thunderbolt Bus: iMac, Apple Inc., 39.2
Thunderbolt Device: Drive Dock, Other World Computing, 1, 25.1
Click to expand...

Edit: So as not to sidetrack the discussion in this thread, I’ve created a new thread in the Mac Apps Forum about Unigine Heaven & Valley crashing on launch. Please post any replies there.
 
Last edited:
Colonel Blimp said:
My 2019 iMac with Vega 48 arrived yesterday. I had hoped to post some benchmarks here, but Unigine Heaven 4.0 and Valley 1.0 (the current versions) are both crashing immediately upon launch, upon both my iMacs (2015 and 2019) running macOS 10.14.4.

My 2015 iMac used to be able to run these, and other folks seem to be posting Unigine benchmark results, so what’s going on? I searched Google, DuckDuckGo, and the MacRumors Forums and found nothing similar.

It’s not a hardware problem, since it affects both my 2015 iMac with M395X and my 2019 iMac with Vega 48.

It might be an incompatibility with macOS 10.14.4 (the 2015 iMac is running build 18E226 and the 2019 iMac shipped with build 18E2034), although that seems unlikely. (Are you all able to run Heaven and Valley in macOS 10.14.4?) Or it might be some strange software incompatibility on my iMacs, as I migrated my apps and settings from the 2015 to the 2019 iMac via Migration Assistant.

Here’s a typical crash report. Heaven or Valley, 2015 or 2019 iMac, it’s always the browser_x64.macos process that crashes in thread 0 with segmentation fault 11. Can any of you make sense of this?
Click to expand...
I'm getting the same error.
 
jerwin said:
I'm getting the same error.
Click to expand...
Jerwin, are you running macOS 10.14.4?
IngerMan said:
Thats odd I just downloaded Heaven and Valley this week while on 10.14.4 and had no issues.

You are getting the downloads from here https://benchmark.unigine.com/heaven
Click to expand...
Yes. My installed Unigine apps worked previously, but to rule out any possible recent corruption of my installation, I re-downloaded and reinstalled Heaven, and I still get the same crash.
[doublepost=1555071181][/doublepost]
bondavi said:
Unboxed my i9 and ran benchmarks, also my old 2017.

2017: i5 3.8 32GB, 2TB Fusion, Radeon 580
2019: i9 3.6 40GB, 512 SSD, Radeon 580X

Heaven Benchmark:
See below.
Click to expand...
Bondavi, what version of macOS were you running on your 2017 and 2019 iMacs when you ran those benchmarks? Heaven is crashing on my 2015 and 2019 iMacs running 10.14.4, and jerwin is getting the same error.

This is very strange.
 
Last edited:
CWallace said:
They did just publish OpenCL and Metal benchmarks: https://barefeats.com/imac-5k-2019-performance-eval.html
Click to expand...

that page they posted near release of these machines is near useless. it relies on numbers posted by other people. It smacks of desperation from a site I normally rely on doing good work. The "we have to post something now!" instead of their usual on hands detailed comparisons.

What I am surprised at is bondavi's report where is 580 vs 580x numbers show no real difference. granted it is for one test but that isn't what I was hoping for.
 
Colonel Blimp said:
My 2019 iMac with Vega 48 arrived yesterday. I had hoped to post some benchmarks here, but Unigine Heaven 4.0 and Valley 1.0 (the current versions) are both crashing immediately upon launch, upon both my iMacs (2015 and 2019) running macOS 10.14.4.

My 2015 iMac used to be able to run these, and other folks seem to be posting Unigine benchmark results, so what’s going on? I searched Google, DuckDuckGo, and the MacRumors Forums and found nothing similar.

It’s not a hardware problem, since it affects both my 2015 iMac with M395X and my 2019 iMac with Vega 48.

It might be an incompatibility with macOS 10.14.4 (the 2015 iMac is running build 18E226 and the 2019 iMac shipped with build 18E2034), although that seems unlikely. (Are you all able to run Heaven and Valley in macOS 10.14.4?) Or it might be some strange software incompatibility on my iMacs, as I migrated my apps and settings from the 2015 to the 2019 iMac via Migration Assistant.

Here’s a typical crash report. Heaven or Valley, 2015 or 2019 iMac, it’s always the browser_x64.macos process that crashes in thread 0 with segmentation fault 11. Can any of you make sense of this?
Click to expand...

Is it the i5 or the i9 you finally got? missing some recompilation on the i5 + vega side for the new post I Want to create
 
jerwin said:
I'm getting the same error.
Click to expand...
Jerwin, does logging in as another user enable you to run Heaven and Valley?
Colonel Blimp said:
…Unigine Heaven 4.0 and Valley 1.0 (the current versions) are both crashing immediately upon launch, upon both my iMacs (2015 and 2019) running macOS 10.14.4.

My 2015 iMac used to be able to run these, and other folks seem to be posting Unigine benchmark results, so what’s going on?

…it might be some strange software incompatibility on my iMacs, as I migrated my apps and settings from the 2015 to the 2019 iMac via Migration Assistant.

Here’s a typical crash report. Heaven or Valley, 2015 or 2019 iMac, it’s always the browser_x64.macos process that crashes in thread 0 with segmentation fault 11. Can any of you make sense of this?
…
Click to expand...
I’ve found that if I log out of my account and then log in as the Guest User or as a new user, Heaven and Valley will run.

If I’m logged into my own account, they crash. I’ve tried deleting the Heaven and Valley folders in Application Support (as well as the only other bits I could find in my ~/Library folder with "com.unigine" in their names), but to no avail.

Do any of you have a clue what might be going on?
 
Colonel Blimp said:
Jerwin, does logging in as another user enable you to run Heaven and Valley?

I’ve found that if I log out of my account and then log in as the Guest User or as a new user, Heaven and Valley will run.

If I’m logged into my own account, they crash. I’ve tried deleting the Heaven and Valley folders in Application Support (as well as the only other bits I could find in my ~/Library folder with "com.unigine" in their names), but to no avail.

Do any of you have a clue what might be going on?
Click to expand...

Please Colonel blimp post your problem on another thread! Here we are ONLY interested on the outcome for the original post “
580X Vs Vega 48“.

The community will thank you!

Regards
 
rvivancoITA said:
Please Colonel blimp post your problem on another thread! Here we are ONLY interested on the outcome for the original post "580X Vs Vega 48". The community will thank you!
Click to expand...

He's trying to provide exactly that (benchmarks for the Vega 48), and I thank him for this.
 
Last edited:
  • Like
Reactions: Colonel Blimp
Colonel Blimp said:
Jerwin, does logging in as another user enable you to run Heaven and Valley?

I’ve found that if I log out of my account and then log in as the Guest User or as a new user, Heaven and Valley will run.

If I’m logged into my own account, they crash. I’ve tried deleting the Heaven and Valley folders in Application Support (as well as the only other bits I could find in my ~/Library folder with "com.unigine" in their names), but to no avail.

Do any of you have a clue what might be going on?
Click to expand...

I thought I would just give one possible hope.

To remove all System files related to the App in finder, you need to hit the + button on the upper right, then on the far left (name) choose System Files than (Matches) Are Included.

I would erase everything related to the app then try a new install

Screen Shot below showing the search sys files

Screen Shot 2019-04-13 at 9.44.13 AM.png Screen Shot 2019-04-13 at 9.44.49 AM.png
 
Last edited:
Bohemien said:
He's trying to provide exactly that (benchmarks for the Vega 48), and I thank him for this.
Click to expand...

Please do not get me wrong, i really appreciate the efforts he is doing, but with the scope of having this topic in order would be nice to read only the topic related about the benchmark, then i will recommend to open another thread about this issue so someone else experiencing the same problem would find immediately the solution...that's all..
 
  • Like
Reactions: Bohemien
rvivancoITA said:
Please do not get me wrong, i really appreciate the efforts he is doing, but with the scope of having this topic in order would be nice to read only the topic related about the benchmark, then i will recommend to open another thread about this issue so someone else experiencing the same problem would find immediately the solution...that's all..
Click to expand...

Ah ok, you just came across a bit harsh to me in the first place. :)

Problem is, nobody really seems to be able to provide what the OP was asking for so far. Most of the review sites seem to have received the i9/Vega configuration, there's very little about the 580X, and no direct comparison between the two GPUs. At least in this French review, there are some comparisons between the 2018 iMac with Radeon 580 and the 2019 Vega 48 config.

Of course, someone would have to have the exact same configuration(s) except for the GPU to provide some reliable test data, and do some typical application tasks to evaluate the real-life difference.

Are there users of Capture One Pro here? Maybe you could perform this test on your machines and post the results? Or even perform the same export task with LR, or On1, Luminar, DXO, whatever you're using (if that software uses the GPU for exporting)?

(My MBP 2011 with i7/2.2GHz and Radeon 6750M completes the export in 3:45 with GPU enabled, 3:20 without GPU - I guess the GPU is too old to provide any benefit to the processor for exporting.)
 
Last edited:
  • Like
Reactions: jerwin
Loa said:
Thanks for the link, but sadly there's not a single gaming comparison between the 580X Vs Vega 48. This is what we're waiting for!
Click to expand...

Ah sorry, from your original post I thought you were also interested in the performance for photo editing. At least that’s what would interest me most. ;) (I’m a console gamer)

Did you see this video yet? It tests the i9/Vega with focus on gaming:


Sadly, as all the reviews so far, there's no comparison of the GPU options for the i9. But they compare the Unigine Heaven score for the 2017 iMac with the Radeon 580 (1041) vs. the i9/Vega (1713), that might be some indicator.

In this post, @Kaelis posts his Unigine Heaven result from the i5/580X config: 1156, that would be within what's to expect for the 580X over the 580 (if the rumor of the 100MHz higher clock speed is true).

Also in the French review, there are some gaming benchmarks, with the 2017 i7/R580 being included in some of them. Of course the CPU also plays a role, but still, it might serve as some basic indicator. Here's a Google translation of their conclusion:

Overall, the difference with the 2017 models remains measured especially on the entry level, where we earn just a few FPS: a 560 and a 555X are almost equal game for example, and the difference is sometimes rather at the level of CPU - but not all games use 4 or 6 cores. On the 21.5 "iMac, thanks to its very efficient memory bandwidth, the Vega 20 comes sometimes to tease the 580, which was the high-end 27" of 2017, not bad! Finally, the Vega 48 appears in the lead, sometimes with a short lead, sometimes with impressive scores-especially if Metal is supported, apparently.
Click to expand...

I guess the problem is that all the review sites seem to test the i9/Vega configuration only... there is one video testing the i9/580X (not for gaming though), but I haven't found one single comparison review between those two configurations.

Found another gaming performance test for the i9/Vega:

 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back