[Brian Jones]

without the image I don’t know but I’m guessing it’s pretty large to show a lot of detail at that render size, so take a look at your material’s Editor tab there is a Texture Preview size there (probably set to Default) which is the size you are seeing in the viewport (with the accompanying blurriness). To match that you would have to scale down your original texture image to match the default (which is likely 256×256) then it should render like it looks in the viewport

[Brian Jones]

if you are talking about the axis and horizon lines (rather than lines on the model) perhaps it is the scale of the render (or the scale you are looking at it in the render window), I noticed those lines disappeared if I scale down the render enough to see it all since the render size is relatively large.

[Brian Jones]

It rendered black initially since the image “model_texture.jpg” wasn’t there but when I substitute another I’m seeing the same thing as before, the viewport and render look identical (even without Enhanced Open GL turned on in the render (Render Settings/Hardware) when Enhanced OGL is on in the Viewport – nothing fancy in reflectance, noises etc. etc. so no surprise)

[Brian Jones]

looks identical to me (simple tests – I never hardware render usually) – if it’s different for you perhaps you are not matching the Enhanced OGL in the render settings to the viewport settings – otherwise have to see the scene file.

[Brian Jones]

regular animation into Unity seems to be easy but PLA needs a trick (according to a quick search) this tut from DigitalMeat might help

https://www.youtube.com/watch?v=r80iOjhjh1s

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Brian Jones]

no ideas but what are you exporting to?

[Brian Jones]

en/dis-abling Dynamics in the projects settings is not the way to go at all (particularly if you want to do staggered objects later). Remove that and keyframe in the dynamics tag on the card (Cube in this case) and, in this case, either keyframe the Enabled parameter (unchecked/checked) or the Dynamic parameter (Off/On) when you want the cube to start swinging.
Dynamics will always require you going back to the beginning of the timeline unless you Cache the dynamics (Dynamics Tag/Cache) – there are options in there to cache all dynamic objects or only ‘this one’. Cached dynamics will play like you want and you will be able to scrub through.

Here’s an example with two cards, the left one is not cached and starts at frame 31 and the right one is cached and starts at frame 60. If you play it all should be ok but if you scrub through only the right one should work correctly.

11355_connectorwithdelay2.c4d.zip

[Brian Jones]

it might be where you are placing the keyframes and the shape of the F-Curve between the Off and On keyframes – might have to see the file

[Brian Jones]

putting an image in the luminance channel is a probable start

[Brian Jones]

while you are reading in the GI section make sure to check out GI Portals which are used to increase quality/decrease render times when lighting from outside to the inside.