Forum Replies Created
-
AuthorPosts
-
Holt_InteractiveCustomer2020-08-10 at 2:09 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31326Holt_InteractiveCustomer
Brilliant! That did the trick. Seak Peek and App Manager are both working properly.
Thanks so much for your help with this. I really appreciate it. This tower has 4X the RAM of any other PC I’m using, so it’s great to have it in the workflow now.
Cheers!
2020-08-10 at 1:58 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31325Holt_InteractiveCustomerI attempted the copy and rename with admin rights, and it returned an error message saying that a file name “hosts” already exists in that folder. I searched for “hosts” in that folder with “visible or invisible” enabled and found the invisible file that was zero bytes (weird). So I’ve deleted that file, duplicated “hosts~orig” and renamed it “hosts”. I’m going to restart now and send a terminal output in a new post soon.
Holt_InteractiveCustomerThank you for the link. We will keep tweaking our file and if our best effort is unacceptable to our client, then we will proceed with this option.
2020-08-10 at 12:49 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31320Holt_InteractiveCustomerI used Go to: /private/etc/hosts and here’s a screenshot of what’s inside /etc/ but (un)surprisingly, there isn’t a host folder located there.
2020-08-07 at 5:29 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31279Holt_InteractiveCustomerOkay, just replaced that python script, and here’s the attached output.
2020-08-07 at 4:10 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31275Holt_InteractiveCustomerCool, thanks Ivan. I’m running 3.3.0 as of June 30th.
2020-08-07 at 3:28 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31271Holt_InteractiveCustomerI moved server.py outside of the addons folder and ran Blender from Terminal. The output is attached. Thank you for your continued assistance.
Holt_InteractiveCustomerWould you be ale to provide a link to pricing for a technical support plan? I don’t think the bean counters will let me upgrade to enterprise right now. Thank you.
Holt_InteractiveCustomerSure thing. I’m in the middle of revising my .blend file and Puzzles to make everything cleaner and more organized. I can provide a link to the published file, but I’d rather get that to you outside of forums as my client is confidential.
2020-08-04 at 8:03 pm in reply to: Trouble running examples on cdn.soft8soft.com/demo/examples/index.html #31162Holt_InteractiveCustomerThese examples work in macOS High Sierra with Java 8 Update 261 installed.
2020-08-04 at 5:55 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31159Holt_InteractiveCustomerAh! Those tricky tricksters; you’ve got to hold down the alt key as well.
Alright, here’s a screenshot of those contents.
Holt_InteractiveCustomerAfter some trial and error I have found that the default setting of “Orbit” in the Verge3D Settings inside of Blender’s Camera Settings needs to be changed to “Flying”, which gets rid of this camera snapping behavior.
To clarify my setup, I’m using the Puzzle “tween camera to: position of “Metaball” look at “Object” in X sec” to move the only camera in the collection to specific metaballs that have been placed in front of corresponding objects I want the camera to move towards. Metaballs won’t render, so they’re great for moving the camera to certain positions without having to enter in XYZ coordinates.
You can tweak the target location for the camera by moving the object’s origin, but you have to move the 3D cursor to the desired location first, and then Set Origin > Origin to 3D Cursor.
Unfortunately, this method removes rotational constraints. So if those are necessary, then this method may not be a good solution.
Holt_InteractiveCustomerAfter some trial and error I have found that if the default setting of “Orbit” in the Verge3D Settings inside of Blender’s Camera Settings is changed to “Flying”, it resolves the camera snapping behavior, but it also removes rotational limits and the ability to move the camera around the collection’s center.
I’ve tried the other options for Controls from the pulldown menu, and Orbit provides the desired control, but the camera snapping is something I will have to fix in order to meet my client’s request for interface behavior.
Any tips that you could provide to remove or greatly reduce camera snapping would be greatly appreciated.
2020-08-03 at 6:04 pm in reply to: Localhost refused to Connect with Chrome 83.0.4103.61 on macOS High Sierra #31096Holt_InteractiveCustomerThis is a strange file path. I went looking for it, and I cannot find that directory. There isn’t a Library folder in my USER folder. I searched for invisible files and it did not show up, under any term used in the folder names of that file path.
-
AuthorPosts