Buildbox 3d Viewport Bad Performance

Hi,

I'm using an iMac (Retina 4K, 21.5-inch, 2017) and I'm experiencing really bad performance with Buildbox 3D Free version in the Scene Editor when adding 3d elements in a scene. Trying those templates ''Dagger Toss'' and ''Adventure'' is unworkable for me and moving the camera or any asset is extremely slow. Any input?

Regards,
Francis

 

I have the same issue with MacBook pro-2017. I think it's just the hardware of the computer not strong enough.

 

With the same iMac, I'm Working with Unreal Engine on several projects for the job with massive amount of stuff on stage and I don't have this issue.
Is it an issue with Buildbox and how 3d assets are handled? Is there any way the performance can be increased?

I would like to come back to BuildBox but with this issue I cannot consider it.

 

That's strange, I have an iMac 4k 21.5 2015 and build box runs smoothly

 

Performance is very slow on my MacBook Pro - 2019 i9 with Radeon GPU...extremely hard to use the editor for my project...just so slow

It is the Scene Editor that runs very slow...I do not think my project tis overly complicated...and I am only using Assets (Basic Shapes) that y9ou create from BuildBox Asset library...but I do have about 8 Squares and 4 or 5 other shapes in the scene on a twisty road template and the performance in the Scene Editor starts to crawl...

 

You can use the Adventure template and add/remove/Move the camera Smoothly?

 

That's about What I'm experiencing also

 

same here on windows runs amazing smooth but the preview little bit laggy.
on the mac runs very slow but on preview runs smooth

 

Yep

 

Ok I can confirm that. Using Bootcamp on my iMac and Buildbox 3d scene editor runs good on windows but Preview is slow.
On iMac Scene Editor is unworkable with Adventure template but Preview runs perfect.
Also each time I quit Buildbox on iMac I have an warning saying that the program as closed in an unexpected way (Sample next
_______________________________________________________
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

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

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

VM Regions Near 0x18:
___________________________________________________

Any DEV can input on this please? Could it be related to the Metal technology? I can provide the complete warning message.

It's a no go for me right now if I cannot have a stable development environment lol.

 

Hey there! Checking into these issues. Looks like could be Radeon or Retina dependent. Will advise once we know more

 

Thank you

 

Hiya, I've just reinstalled the demo on my imac and the editor viewport is still very slow for bigger scenes... Any input on future fixes?

 

Still having issues? Strange, I don’t seem to have issues myself. I do recommend sending an email to support@buildbox.com.
It might help to narrow down the issue in the very least.

 

Yes I'm still having the issue which is sad! Really wanna get back to Buildbox but this issue is a real pain.

Any news about that Sean?

 

I use an iMac and I only experience lag in the preview screen if I have the collision icon active in BB while in preview. Once I turn it off the lag disappears. Do you have the collision turned on in your BB while you are previewing your game?
I see the the same thing in my MacBook Air.

 

No the collision are not visually active

 

From what I can tell so far it seems to be related to the textures used on 3d assets. When removing the textures from the 3d assets on the 'Dagger Toss' and 'Adventure' templates it solve the issue and the viewport performance is really good.
The 'Martian Marathon' template use a lot of assets on the scenes and run smooth in the viewport though!?... I looked at the textures and the 3d assets seems to all share the same one which is small and lead to a good viewport performance.

Sorry to bother with that issue but I'm working with the Unreal Engine on a daily basis with that same computer, on scenes with a lot of textures and I don't have this kind of issues.
I hope you will find an solution for that. I would be happy to be a returning developer

 

I’ve forwarded this again for you. I can see the issue you have when I tested it, I have also found some other stuff in relation to textures. So I would say that it won’t be too much longer on seeing improvements with this issue.

 

Thank you