You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi! i've been eyeing drei since i've started using three.js, & i've finally gone through the process of getting up to speed with react & r3f to be able to take advantage of this project. since i'm starting from scratch, i went with the decision of targetting react 19 after finding out r3f has betas & RC's out to support the new react version.
however, after plugging in various drei components like MeshPortalMaterial & RenderTexture (as well as EffectComposer, but i'm not sure if this is the correct place to ask), they required manual patches to their usages of __r3f as they tried to access undefined properties (e.g. object.parent is assumed to be Object3D with another __r3f property, but is actually an object with a object property that points to the Object3D).
my question is, am i configuring/doing something wrong? or are the utilities here not compatible with my setup yet? the following are some package versions that might be of interest:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
hi! i've been eyeing drei since i've started using three.js, & i've finally gone through the process of getting up to speed with react & r3f to be able to take advantage of this project. since i'm starting from scratch, i went with the decision of targetting react 19 after finding out r3f has betas & RC's out to support the new react version.
however, after plugging in various drei components like
MeshPortalMaterial
&RenderTexture
(as well asEffectComposer
, but i'm not sure if this is the correct place to ask), they required manual patches to their usages of__r3f
as they tried to access undefined properties (e.g.object.parent
is assumed to beObject3D
with another__r3f
property, but is actually an object with aobject
property that points to theObject3D
).my question is, am i configuring/doing something wrong? or are the utilities here not compatible with my setup yet? the following are some package versions that might be of interest:
Beta Was this translation helpful? Give feedback.
All reactions