Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac build tests #10

Open
BenRacicot opened this issue Aug 31, 2019 · 18 comments
Open

Mac build tests #10

BenRacicot opened this issue Aug 31, 2019 · 18 comments

Comments

@BenRacicot
Copy link

BenRacicot commented Aug 31, 2019

Hey @maikramer. I've opened the latest Dropbox build from @fouman75.
I believe it is completely non-functional:

2016, 15’’ Macbook Pro
MacOS 10.14.6
16GB ram
460 Radeon Pro 4GB

Screen Shot 2019-08-31 at 8 06 09 AM

The above is how it looks when opening the app, then the red text is from: adding a square png of rocks as a height map image -> clicking save

Also, which network requests is Materialize asking for? Should I wireshark them and list?
Screen Shot 2019-08-31 at 8 11 26 AM

When unzipping that Dropbox file materialize_0.3.7.app.zip it does not create the expected folders at this path ~/Library/Logs/BoundingBoxSoftware/Materialize/ or the log file.

@fouman75
Copy link

The log file should be produced when running the app. Next to the red message, there is a "Open Log File" button. Can you locate the file from there and attach it here?

@BenRacicot
Copy link
Author

BenRacicot commented Aug 31, 2019

@fouman75 thank you for explaining, I hadn't noticed that. I've attached the Player.log file.

I'm seeing two things
16: Plugins: Couldn't open libc, error: dlopen(libc, 2): image not found
May be causing
43: NullReferenceException: Object reference not set to an instance of an object

@fouman75
Copy link

  • For network access, I believe it might be because it's a development build and you can attach a debugger to the running application. Did you notice that message when running the previous version?
  • For "Couldn't open libc ...", I have the same message in my logs. We should disregard this for now as I don't think it's relevant.
  • I looked at the code a bit and I see a problem with the code that saves textures. I have the same error on my side.

But before anything else, I'm very confused with your screenshot. This is not how the app should look at all.

This is what it should look like:
Screen Shot 2019-08-31 at 3 55 12 PM

Can you confirm if the app looks like this on your side? There might be something really wrong if it's all black like your screenshot, regardless of the small problem with saving.

I know the app is not the friendliest to work with. Usually you would do the following:

  • Open (O) a texture in the DIFFUSE box.
  • Use the "Create" button for Height map / Click "Set as ..." when done editing.
  • Use the "Create" button on any other maps ...

At any one point, click "Show Full Material" to see the results on the cube/sphere/...

Please confirm if you can at least get the basic workflow going of seeing the material in 3D.

@BenRacicot
Copy link
Author

BenRacicot commented Sep 2, 2019

Yes always black, I do not see the blued image and 3D movable pane. I had watched a YT tutorial on Materialize and have been trying his workflow. Nothing seems to change anything about my black screen or produce files. Perhaps @maikramer will recognize the issues from his previous experience?
Also, had you got this to work on you MBP? I was wondering if it's expecting DX9 or something to render the 3D view of the image. You never see a flat black background?

Here is the result of your outlined flow:
Screen Shot 2019-09-02 at 8 39 17 AM

When I hit save on any process I get the OS file save prompt but no file exists when saving:
Screen Shot 2019-09-02 at 8 41 34 AM

No error logs on these flows except saving a file (from diffuse)
Screen Shot 2019-09-02 at 8 42 49 AM

diffuse-save-error.log

@fouman75
Copy link

fouman75 commented Sep 2, 2019

I don't have a MBP and I've never encountered the black screen problem (using iMac). I know another user reported the same problem a while back but there was no follow up. Since I don't have a MBP, there is only so much I can do ...

I have updated the build in dropbox for now. I changed the following:

  • Fixed the saving bug
  • I switched the app to fullscreen mode and activated a bunch of graphics/resolution options. It might be a resolution issue on MBP. That's the only thing I can think of right now. You should get a new window when starting the app to select your resolution. Try with default settings first and if it doesn't work, try different resolutions or switching from fullscreen (command-f) and resizing the window.
  • Note that log file will be in ~/Library/Logs/Bounding Box Software/Materialize (with spaces).

Fingers crossed!

@maikramer
Copy link
Owner

maikramer commented Sep 2, 2019 via email

@fouman75
Copy link

fouman75 commented Sep 5, 2019

@maikramer I can't seem to push a branch to your repo.

ERROR: Permission to maikramer/Materialize.git denied to fouman75.

Anything you can check on your side? I've been checking my ssh keys and everything seems in order. Let me know!

@maikramer
Copy link
Owner

maikramer commented Sep 6, 2019 via email

@BenRacicot
Copy link
Author

@fouman75 Saw this article on how to contribute to open source on css-tricks. It has guidance on the PR setup. I hope you are willing to keep helping this project, it needs your skills.

@fouman75
Copy link

@BenRacicot thanks for the link, I figured it out.

Did you get a chance to test the version I posted 2 weeks ago? Just curious if it's working 😁

@BenRacicot
Copy link
Author

Hey @fouman75 thank you for asking. I thought I had until you asked. This new version did give me options such as resolution and windowed mode upon startup. However, the resolution is not scaled appropriately:

Screen Shot 2019-09-18 at 6 08 54 PM

This is my chosen windowed -> 1440 resolution. The rocks image was uploaded in the first pane and saved. The outputed, saved image is what is shown.

I do not have a ~/Library/Logs/Bounding Box Software/ folder.

@fouman75
Copy link

@BenRacicot Did you try other settings? Notably without windowed mode (unchecked) and resolution of 1920x1080 if available (or any 16:9)? Without even loading any images, if it's all black, it's not working. Right from launching the app, you should see the unity logo, then a bounding box splash screen and then you should see the UI with a 3D box and gradient background.

As for the log folder, I can't say. I just ran the app from scratch and I have the folder on my system:
From Terminal:
cd ~/Library/Logs/
cd Bounding\ Box\ Software/

Or in Finder under Users//Library/Logs ...

Let me know! :)

@sejef
Copy link

sejef commented Dec 14, 2019

Hi,
I dowloaded and tested @fouman75 's dropbox version and had the same problem as @BenRacicot : black background and not usable (but not crashing) on my rig : 10.14.6 / RX580.

Disabling the "Enable Post Processing by default" option in the settings (down right button) fixed the problem and displayed the material preview and the background at startup. I then successfully loaded a diffuse texture and created the height and normal maps before re-enabling the post-processing in the Post Process button (up lefty).

An important point : Unity is trying to phone cdp.cloud.unity3d.com port 443 for usage and stats without any warning. Thats raised some concerns about Privacy.

Thanks @fouman75 for your work.

@fouman75
Copy link

@fastfuel This is great, thanks for finding the issue! I made a new build where PostProcessing is now disabled by default.

I have also removed a setting to "hopefully" prevent Unity's data gathering.

The built is on Dropbox

@maikramer:

  • I think we should close this issue. If new bugs occur, they should go in separate threads.
  • Will you be hosting the OSX file on this repo as well?
  • I didn't want to merge the OSX settings I changed into the main branch. Should we have a different branch for OSX? Not sure it would really hurt other platforms but don't really want to disable automatic PostProcessing for all because of a MacBook Pro issue.

@sejef
Copy link

sejef commented Dec 15, 2019

@fouman75

This is great, thanks for finding the issue! I made a new build where PostProcessing is now disabled by default.

Working for me, but the Materialize Configuration screen (with resolutions) is not displayed any more, even with option key pressed at startup :/

I have also removed a setting to "hopefully" prevent Unity's data gathering.

I don't see any more call in the log file. Thanks !

@fouman75
Copy link

@fastfuel For the Config screen, that feature has been deprecated by Unity. I turned it on to see if the black problem was tied to the resolution. I turned it back off in the latest build. I can activate it again if needed. In the current build, you can use Command-F to get out of full screen and resize the window if needed.

@maikramer
Copy link
Owner

Hi, i`m merging the pull request and i will add some new features also.
@FourMan I will try to add the Unity Post Processing stack as a option, will try to add it today.

@maikramer
Copy link
Owner

@fastfuel This is great, thanks for finding the issue! I made a new build where PostProcessing is now disabled by default.

I have also removed a setting to "hopefully" prevent Unity's data gathering.

The built is on Dropbox

@maikramer:

* I think we should close this issue. If new bugs occur, they should go in separate threads.

* Will you be hosting the OSX file on this repo as well?

* I didn't want to merge the OSX settings I changed into the main branch. Should we have a different branch for OSX? Not sure it would really hurt other platforms but don't really want to disable automatic PostProcessing for all because of a MacBook Pro issue.

Can you open a pull request with the options you changed? then i can check and see if i will merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants