[Jens Mock]

just a quick feedback how I managed to circumvent my problems:

the flickering lights were caused by the spotlight in the scene – by switching off ‘cast shadow’ this was resolved.
The other thing was the weird looking DoF – the problem was discussed on the Adobe forum and can be read here:
https://forums.adobe.com/servlet/JiveServlet/downloadImage/2-5192466-314377/450-197/blur.JPG

which in conclusion is caused by (the lack of power of) the graphic card.
there is no other way around NVIDIAs cuda-technology 😉

and thanks for your feedback, Walter

[Jens Mock]

just a quick feedback how I managed to circumvent my problems:

the flickering lights were caused by the spotlight in the scene – by switching off ‘cast shadow’ this was resolved.
The other thing was the weird looking DoF – the problem was discussed on the Adobe forum and can be read here:
https://forums.adobe.com/servlet/JiveServlet/downloadImage/2-5192466-314377/450-197/blur.JPG

which in conclusion is caused by (the lack of power of) the graphic card.
there is no other way around NVIDIAs cuda-technology 😉

[Jens Mock]

thanks for the hints but I think I can exclude the disk cache. I rendered the clip at a freshly started machine, pretty much unused for that day (this phenomenon occurs independently of day and workhours).

But the DoF can be sth. to look further. I’ve read somewhere (here) that it’s not supported but you’re right, I can switch it on/off – the ‘real’ reason I precomped everything was that when I had the DoF turned on, the plain textlines looked as if you blur a layer in photoshop and switch the layermode to ‘dissolve’ and set the transparency to sth. like 40% – far from anything useful :-/

maybe some details to the precomps:
within each of them I put the camera plus the two lights (plus text) so in the main comp they are not really necessary anymore (bit still there and turned on). I tested if it makes any difference if lights/camera in the mainComp are on or off, if it’s necessary that the preComps are 3d-layers (collapsed) or not and I tried what happened if everything is turned on – there are always blinking letters.

I will go for the updates and ask the administrator about that … (not the solution I hoped for)

[Jens Mock]

hi folks,

I just found the solution to my problem and the above mentioned expression did it, just modified the following:

l = thisComp.layer("My3DLayer"); l.toComp(l.anchorPoint);

replaced the Anchor Point by pigwhipping either the Attach Point or the Feature Center of the trackpoint and that’s it. May seems obvious but it needed some days of rest to let me see it :-}

Jens

[Jens Mock]

both propositions get me quite close to what I try to achieve but don’t work properly for me.

I have a 3d-layer (a pre-comped map) with a camera flying around and want a 2d-layer (solid with cc sphere applied to) staying at a certain point on the map from the viewpoint of the active camera.
I somehow managed to apply tracking data to the solid but since it happened with a lot of trying, deleting and retrying I couldn’t figure out how that actually took place. I was even able to reproduce that once more but let me down the third time. 🙂
What surprised me even more was that the data came from a still-image (and no script involved so far)

Anyway, a script would be an even more elegant way of solving my problem but those from Darby and Jan don’t keep the sphere on its place like the tracking points do.

a solution to either one way is highly appreciated; maybe it’s just a tweaking on one of the scripts above but I’m totally blindfolded to do that myself

thx in advance, Jens