Orthografic camera, doesn't recognize arguments

[JaimeTorrealba]

Describe the bug

I was trying to follow this guide https://threejs.org/manual/#en/shadertoy. but the Orthographic camera look like doesn't receive the arguments. You can see in the log of the reproduction link, it comes with some values really random like:
bottom: -379.5 when I pass 1

Am I doing something wrong? or is a TresJs problem?

Reproduction

https://stackblitz.com/edit/tresjs-minimal-reproduction?file=src%2FApp.vue

Steps to reproduce

You can try to pass the arguments :args or individual parameters, look like it doesn't accept it

System Info

  Binaries:
    Node: 20.19.1
    npm: 10.8.2
  npmPackages:
    @tresjs/cientos: ^4.0.3 => 4.0.3 
    @tresjs/core: ^4.3.2 => 4.3.2 

Used Package Manager

npm

Code of Conduct

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[alvarosabu]

Hi @JaimeTorrealba thanks for opening this ticket. I don't see info of the version you are using on the System Info. Can you confirm if you still have that issue with the lastest next?

pnpm install @tresjs/core@next

We made some improvements on the camera management, hopefully, now the orthographic one should work as expected.

[JaimeTorrealba]

Hi  @alvarosabu I added the system info and I tried with the @next version and it works well

[Tinoooo]

This is possibly related to #978.

[dataexcess]

Hello.

I am confused is this only fixed when installing

pnpm install @tresjs/core@next

because it seems when I do that it breaks a lot of other tresjs stuff in my project...

I am running these currently:

"@tresjs/cientos": "^4.3.1",
"@tresjs/nuxt": "^4.0.0",

thnx for clarifying

[alvarosabu]

@dataexcess We're working on the documentation for v5, which includes a migration guide. I suggest waiting for the alpha or RC.

[dataexcess]

So I'm developing a 3D editor and I need a Hybrid Camera that is able to switch from perspective to orthographic projection by a simple toggle switch... (as can be seen in Blender etc.) I'm having a hard time since I want to keep using OrbitControls, but that one expects either a PerspectiveCamera or an OrthographicCamera (not a Camera, so subclassing Camera seems not the way to go), So then I simply went for having two instances and syncing their position and lookAt methods. The problem seems to be that I simply cannot set any left, right, bottom, top on the raw THREE.OrthographicCamera instance (i use in a tresjs primitive) it always resets to some specific values - and I do not understand why. Could you explain to me so I can work on a fix OR give me an ETA for v5 to release? Much appreciated! thnx

[dataexcess]

Ok I noticed the default values injected by TresJs in the ortographic camera every frame can be bypassed when supplying the orthographic camera with :manual="true" argument. And so it is kind of working.. BUT now when I try to move the objects in the scene with a TransformControl component the camera moves while moving the transform around. So I think I have probably broken some tres-js behind the scenes stuff doing this... here's my Camera.vue class... (isPerspective is just a boolean inside a composable so I can access it globally in my codebase)

<template>
	<TresPerspectiveCamera ref="perspectiveCamera" :manual="true" />
	<TresOrthographicCamera ref="orthographicCamera" :manual="true" />
	<OrbitControls make-default />
</template>

<script setup lang="ts">
import * as THREE from 'three'

// Cameras
const perspectiveCamera = ref<THREE.PerspectiveCamera>()
const orthographicCamera = ref<THREE.OrthographicCamera>()

const { setCameraActive } = useTresContext()
const { isPerspective } = useSceneCamera()

onMounted(() => {
	if (perspectiveCamera.value) {
		setCameraActive(perspectiveCamera.value)
	}
})

watch(
	isPerspective,
	(newVal) => {
		if (!perspectiveCamera.value || !orthographicCamera.value) return

		const fromCam = (newVal ? orthographicCamera.value : perspectiveCamera.value) as THREE.Camera
		const toCam = (newVal ? perspectiveCamera.value : orthographicCamera.value) as THREE.Camera

		toCam.position.copy(fromCam.position)
		toCam.quaternion.copy(fromCam.quaternion)

		// if switching to ortho, adjust frustum to match view
		if (!newVal) {
			const dist = fromCam.position.length()
			const fovRad = THREE.MathUtils.degToRad((perspectiveCamera.value as THREE.PerspectiveCamera).fov)
			const height = 2 * dist * Math.tan(fovRad / 2)
			const width = height * perspectiveCamera.value.aspect

			const orthoCam = orthographicCamera.value as THREE.OrthographicCamera
			orthoCam.left = -width / 2
			orthoCam.right = width / 2
			orthoCam.top = height / 2
			orthoCam.bottom = -height / 2
			orthoCam.updateProjectionMatrix()
		}

		setCameraActive(toCam)
	},
	{ immediate: true }
)
</script>

[dataexcess]

Hi @JaimeTorrealba thanks for opening this ticket. I don't see info of the version you are using on the System Info. Can you confirm if you still have that issue with the lastest next?

pnpm install @tresjs/core@next

We made some improvements on the camera management, hopefully, now the orthographic one should work as expected.

Hello, I'm wondering wether the fix that works for @JaimeTorrealba also works when updating with nuxt?

"@tresjs/nuxt": "^4.1.0-next.1",

I don't believe it doesa