
- Posts: 24
- Joined: Tue Apr 10, 2018 3:27 pm
- Real Name: Dirk de Jong
I've attached a zip file to this post. It contains 2 Fusion comps which include expressions which access the DoD info of a Text+ tool in order to scale or place another object.
At first I was attempting to create this (multiple attempts) in Fusion within the Resolve 15 beta, but I would find it failing to render as expected (preview window ceases to update) and then the UI would become more and more unresponsive, and eventually the app would seem to stop responding altogether requiring it to be Force Quit. So I tried the same thing in Fusion 9 on the same machine and it works as expected without such problems. After importing either of the 2 comps (which were saved out of Fusion9) into Fusion within Resolve 15 my machine shows the symptoms described previously. But I do not believe it to be a compatibility issue bringing the files from the standalone to Resolve 15 since I encountered the same thing trying to create it from scratch in Resolve 15. To see the expected result, open the comps in Fusion9
System Version: macOS 10.13.4 (17E199)
Model Name: MacBook Pro
Model Identifier: MacBookPro11,5
Processor Name: Intel Core i7
Processor Speed: 2.5 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
GRAPHICS
AMD Radeon R9 M370X:
Chipset Model: AMD Radeon R9 M370X
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Dynamic, Max): 2048 MB
Vendor: AMD (0x1002)
Device ID: 0x6821
Revision ID: 0x0083
ROM Revision: 113-C5670E-945
VBIOS Version: 113-C567A1-006
EFI Driver Version: 01.00.945
Automatic Graphics Switching: Supported
gMux Version: 4.0.20 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3
At first I was attempting to create this (multiple attempts) in Fusion within the Resolve 15 beta, but I would find it failing to render as expected (preview window ceases to update) and then the UI would become more and more unresponsive, and eventually the app would seem to stop responding altogether requiring it to be Force Quit. So I tried the same thing in Fusion 9 on the same machine and it works as expected without such problems. After importing either of the 2 comps (which were saved out of Fusion9) into Fusion within Resolve 15 my machine shows the symptoms described previously. But I do not believe it to be a compatibility issue bringing the files from the standalone to Resolve 15 since I encountered the same thing trying to create it from scratch in Resolve 15. To see the expected result, open the comps in Fusion9
System Version: macOS 10.13.4 (17E199)
Model Name: MacBook Pro
Model Identifier: MacBookPro11,5
Processor Name: Intel Core i7
Processor Speed: 2.5 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
GRAPHICS
AMD Radeon R9 M370X:
Chipset Model: AMD Radeon R9 M370X
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Dynamic, Max): 2048 MB
Vendor: AMD (0x1002)
Device ID: 0x6821
Revision ID: 0x0083
ROM Revision: 113-C5670E-945
VBIOS Version: 113-C567A1-006
EFI Driver Version: 01.00.945
Automatic Graphics Switching: Supported
gMux Version: 4.0.20 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3
- Attachments
-
fusion_comps.zip
- (4.98 KiB) Downloaded 85 times