On 28/09/2025 15:42, Bald Eagle wrote:
> yesbird wrote:
>> Bill, could you please look at the browser's console
>> (usually F12) and send me content ?
> 
> Tried again just now - I see no grid or rotation, or controls for zooming or
> panning.
> 
> When I was very new povver, I would draw arrows from the origin to objects or
> light sources to help me find where things were when they were out of view.
> 
> You could also possibly have a labeled grid, and display the center of the
> object in text.  Maybe have a checkbox "Center at origin".
> 
> OK, maybe since a lot of objects are things that sit on a surface, have a second
> checkbox that centers the object, and has its ymin set at 0.
> 
> - BW
> 
> 
> 
> 

Bill, first of all please check if your browser supports WebGL:
https://webglreport.com/

Then select _console_ tab after pressing F12 and look for
errors there.

Axis will act as reference. I will think about centering after
collecting more information and samples.

Pan/Zoom/Scale can be controlled only by the mouse -
this is standard now and I don't want to implement complicated
environment.

Many thanks for testing, wishing well :).
-- 
YB

Post a reply to this message

On 28/09/2025 15:42, Bald Eagle wrote:
> You could also possibly have a labeled grid, and display the center of the
> object in text.  Maybe have a checkbox "Center at origin".
> 
> OK, maybe since a lot of objects are things that sit on a surface, have a second
> checkbox that centers the object, and has its ymin set at 0.
> 

This is the point for discussion: should converter change
object's coordinates or just repack then into other format ?
I guess, this is the editor's function.

Maybe, it will be better just position the camera to look at object
and set acceptable zoom ?

In attachment: 'hand', loaded into C4D.
-- 
YB

Post a reply to this message

Attachments:
Download 'hand_c4d.png' (404 KB)

Preview of image 'hand_c4d.png'

hi,

yesbird wrote:
> ...
> Pan/Zoom/Scale can be controlled only by the mouse -
> this is standard now ...

great !!!  that'll allow me to put the coffee cup and ashtray on the now unused
keyboard </grin>.


regards, jr.

Post a reply to this message

On 28/09/2025 18:13, jr wrote:
> great !!!  that'll allow me to put the coffee cup and ashtray on the now unused
> keyboard </grin>.

I mean lack of GUI.
-- 
YB

Post a reply to this message

On 28/09/2025 15:42, Bald Eagle wrote:
> 
> You could also possibly have a labeled grid, and display the center of the
> object in text.  Maybe have a checkbox "Center at origin".
> 
> OK, maybe since a lot of objects are things that sit on a surface, have a second
> checkbox that centers the object, and has its ymin set at 0.
>

I have improved the default view on loading, now model sits at the
center and fits the screen perfectly.
-- 
YB

Post a reply to this message

yesbird wrote:

> Bill, first of all please check if your browser supports WebGL:
> https://webglreport.com/

Brave supports WebGl1



Sometimes this is the result of older video drivers being rejected by the
browser. Try updating your video drivers if possible.

Also check out Get WebGL, or try installing the latest version of Chrome, or
Firefox.


> Then select _console_ tab after pressing F12 and look for
> errors there.

three.module.js:29414 THREE.WebGLRenderer: A WebGL context could not be created.
Reason:  Could not create a WebGL context, VENDOR = 0x8086, DEVICE = 0x0412,
GL_VENDOR = Google Inc. (Intel), GL_RENDERER = ANGLE (Intel, Intel(R) HD
Graphics 4600 Direct3D9Ex vs_3_0 ps_3_0, igdumdim64.dll -10.18.14.5180),
GL_VERSION = 10.18.14.5180, Sandboxed = yes, Optimus = no, AMD switchable = no,
Reset notification strategy = 0x8252, ErrorMessage = BindToCurrentSequence
failed: .
onContextCreationError @ three.module.js:29414
three.module.js:29414 THREE.WebGLRenderer: A WebGL context could not be created.
Reason:  Failed to create a WebGL2 context.
onContextCreationError @ three.module.js:29414
three.module.js:29414 THREE.WebGLRenderer: A WebGL context could not be created.
Reason:  Could not create a WebGL context, VENDOR = 0x8086, DEVICE = 0x0412,
GL_VENDOR = Google Inc. (Intel), GL_RENDERER = ANGLE (Intel, Intel(R) HD
Graphics 4600 Direct3D9Ex vs_3_0 ps_3_0, igdumdim64.dll -10.18.14.5180),
GL_VERSION = 10.18.14.5180, Sandboxed = yes, Optimus = no, AMD switchable = no,
Reset notification strategy = 0x8252, ErrorMessage = BindToCurrentSequence
failed: .
onContextCreationError @ three.module.js:29414
three.module.js:29414 THREE.WebGLRenderer: A WebGL context could not be created.
Reason:  Failed to create a WebGL2 context.
onContextCreationError @ three.module.js:29414
three.module.js:28990 THREE.WebGLRenderer: Error creating WebGL context.
WebGLRenderer @ three.module.js:28990
three.module.js:28980 Uncaught Error: Error creating WebGL context.
    at new WebGLRenderer (three.module.js:28980:13)
    at init (main.js:50:14)
    at main.js:316:7
main.js:267 Uncaught TypeError: Cannot read properties of undefined (reading
'setSize')
    at onWindowResize (main.js:267:12)



> Many thanks for testing, wishing well :).

Many thanks for writing, and wishing you and everyone else the best in these
crazy times.

- BW

Post a reply to this message

yesbird wrote:

> This is the point for discussion: should converter change
> object's coordinates or just repack then into other format ?
> I guess, this is the editor's function.

I would say it depends on what the user wants.
Blindly converting from one format to another, the computer doesn't "know".

> Maybe, it will be better just position the camera to look at object
> and set acceptable zoom ?

I mean, that's fine for default behaviour, however I'd provide the option to
center in either of the two ways I suggested.

> In attachment: 'hand', loaded into C4D.

So here we have a "part" of what if likely a bigger object / assembly.
It would make sense that it is positioned in relation to the other parts, and so
changing that deletes that very carefully specified position.

Having a coffee mug 100 units in the air and WAY off center doesn't make a lot
of sense.  We'd want to fix that obvious problem so that it doesn;t have to be
accounted for every time we instantiate the mesh, so it would get centered, with
y=0.

For other meshes, where having the center of the object at the origin would make
more sense from a rendering / modeling standpoint, then that would also be a
valid option.


But only the human user can look at that and know for sure.

- BW

Post a reply to this message

On 29/09/2025 00:55, Bald Eagle wrote:
> Brave supports WebGl1
> 
> × This browser supports WebGL 2, but it is disabled or unavailable.
> 
> Sometimes this is the result of older video drivers being rejected by the
> browser. Try updating your video drivers if possible.
> 
> Also check out Get WebGL, or try installing the latest version of Chrome, or
> Firefox.
...
> Reason:  Failed to create a WebGL2 context.

Looks like WebGl1 is insufficient for Three.js and it wants WebGL2.
Did you tried it with Opera ?

"Don't give in without a fight" :).
-- 
YB

Post a reply to this message

On 29/09/2025 01:02, Bald Eagle wrote:
> 
> I would say it depends on what the user wants.
> ...

I absolutely agree with all your statements, let's collect
user's opinions and then make decisions about further development.

The only question I have: how to inform the maximum number of 'povers'
about this service ?
-- 
YB

Post a reply to this message

yesbird wrote:

> Looks like WebGl1 is insufficient for Three.js and it wants WebGL2.
> Did you tried it with Opera ?


Looks to be the same thing.
Tried enabling a thing in Brave to allow WebGL2, but that didn't work.

I'll give it a whirl in Edge since I already have the Win11 spyvirus on my
laptop.

- BW

Post a reply to this message