RobertBillyBob
Senior Member.
You can now right-click on things like objects and tracks to edit them.
Mild inconvenience : the default firefox right-click menu is on top of the edit menu. If you left click the edit menu you can then access it.
You can now right-click on things like objects and tracks to edit them.
It still flashes up the camera in the wrong location for a fraction of a second (much more for longer videos and complex sitches). I'll see what I can do.Sorry, this loads fine and fast for me also. Like Mick, I have a good internet connection (fibre).
This now deleted Reddit thread featured a Piper P28 so I gave it a go with the new flashing PA28 model in Sitrec
Nice, they are now requiring DTLsExternal Quote:
Your post has been removed for not including the time and location of the sighting in the proper format. You must submit your sighting post with the text Time: and Location: on separate lines like this:
"Time: date and time
Location: location of sighting"
Yeah but you can often get away with "around midnight last night" and "mid Nebraska" so it's basically useless and you still have social engineer or sleuth the real details from them.Nice, they are now requiring DTLsExternal Quote:
Your post has been removed for not including the time and location of the sighting in the proper format. You must submit your sighting post with the text Time: and Location: on separate lines like this:
"Time: date and time
Location: location of sighting"
Yeah, this is a bit messed up, I'll fix it eventually so it only displays one (there some complications). I'd set the target object to 0 size for now.One thing is when using camera tracking object and using a plane model, what's the expected flow, set the tracking object to the plane model and the named track to 0 radius? Otherwise you double up on the models..
The Piper model seems to have stopped working..
I'm not seeing that. Can you post a full-screen screenshot, a sitch link, and the steps to reproduce it?Also other models are upside down by default
Can you post a sitch linkthis is what I am seeing with the Piper no model, same with the 737, the line is the cube for tracking object reduced to smallest size
That was a fiddly little bug! Now fixed.I've found that models with blinking lights need the main camera view to be close for it to show up on the look view (unless look view is full screen)
this._object.scale.setScalar(newSize);
[I]// CRITICAL: Force immediate matrix world update after changing scale
//
// When rendering multiple views with different cameras, each view's preRender() sets
// a different scale based on camera distance. However, modifying an object's scale
// does NOT automatically set the matrixWorldNeedsUpdate flag in Three.js. Without
// this explicit updateMatrixWorld() call, the object's world matrix remains stale.
//
// This causes issues in multi-view rendering where whichever view renders second
// experiences incorrect billboard behavior (disappearing at wrong distances). The
// exact mechanism is unclear - it could be related to frustum culling using stale
// bounding spheres, or other matrix-dependent calculations.
//
// Calling updateMatrixWorld() immediately after changing the scale ensures the
// world matrix is current before the renderer processes this object.[/I]
this._object.updateMatrixWorld();
with 2.6.2 I've fixed the issue with the cube appearing over a tracked object.this is what I am seeing with the Piper no model, same with the 737, the line is the cube for tracking object reduced to smallest size
this is what I am seeing with the Piper no model, same with the 737, the line is the cube for tracking object reduced to smallest size
I think that would only affect the lights themselves. We'll see if @jarlrmai can repeat itBased on how far away the Main View is on the screenshot, I suspect the Piper is having the same issue that I mentioned about the Main View distance affecting how a model with lights shows up on the Look View
https://www.metabunk.org/sitrec/?custom=https://sitrec.s3.us-west-2.amazonaws.com/11433/piper example/20251004_173626.jswith 2.6.2 I've fixed the issue with the cube appearing over a tracked object.
I still don't know what's happening with the Piper not working, but try it again, and if you can replicate it, post the sitch link.
No models (or geometry) will display in the case in your sitch. If you set the traverse object to the same path as another object then it will disable the traverse object (otherwise you get two overlapping objects)https://www.metabunk.org/sitrec/?custom=https://sitrec.s3.us-west-2.amazonaws.com/11433/piper example/20251004_173626.js
In this link now, the piper model does not display
Okay I had to change to back to being the named model and not the target model being the plane.
Thanks for the great suggestions. To make sure they don't get lost, can you add them to GitHub as issues? One suggestion/bug per "Issue"I've been using Sitrec a lot recently and some features that would be nice would be
Adding notes (text, links to the Metabunk thread, Reddit, Tweet etc)
Adding a comparison image, ie a screen-grab from the video and steet-view to show that the location matches something if there is anything identifiable in the video
It would be good if there was some way in Sitrec to make the plane light brighter/bigger when it is pointing right towards the camera.
The quibble some people might have with this is that the blue dot is smaller (further away) whereas in the video it is brighter and appears bigger/closer. (Of course, this is because it is the bright forward-facing light pointing towards the camera, which fades out as the plane turns away.)
That sitch is saved with spheres rather than models but I tried using plane models with bright landing lights and they don't seem to be "directional": https://www.metabunk.org/sitrec/?cu...aws.com/5177/Attaching_ DE/20251012_075335.js