Camera360v3 - camera system for VR180 , 360, Fulldome, Cilindrical and Spherical Mirror - Mono and 3D Stereo version)
This product contains a set of popular projections for visualization of various directions, working in Editor, which can be useful in everyday work.
**This product is designed as an optimized solution that uses rendering with a single camera, which means that it will be enough for you to work even on a weak machine.**Help Widget Camera360v3:
Attention: This product does not contain Camera 360v1 and Camera 360v2.
Features:
Raytracing, PathTracing , Lumen working;
VR180, 360, Cylindrical, FullDome, Spherical Mirror - Mono and 3D Stereo;
Works as a render pass for Movie Render;
DLSS, Bloom, AA, Pathtracing, Stereo.
Mega Highresolution for Mono projection ~ 60k maybe more, for stereo 20k
This plugin is focused on ease of operation.
Support JPG, PNG, EXR (Compassion support), BMP
Known issues:
Motion Vector not support (Rendering is based on stopping the frame for subsequent rendering)
To render layers,stencil layer, Alpha use EXR. 2. Support working with rendering layers, stencil layer, Alpha in EXR, but at the moment I’m working on optimizing the solution to speed up the processing processes. Rendering layers in stereo mode for other formats (JPG,PNG,BMP) is still in production. For now, you can work in Mono mode.Stereo mode is supported, but at the moment it is very slow.
ObjectId is not available yet, but I have plans to address this issue.
At the moment, the plugin only works in image rendering mode. I will add the possibility of video conversion later.
I didn’t have a chance to test the work on the Mac.
The plugin is still in production and it will be gradually updated with functionality.
This is the initial version of the plugin, which will be improved for a very long time.
If you need to increase the pixel quality, just increase the size. For example, the default value is 100%, you can raise the quality to 110%, for example, where as a result the pixel quality will be increased by 10%.
You can say it corresponds to r.ScreenPercentage
This option will be activated by default. If earlier we used a 1-to-1 camera size for rendering, for example 1000x1000, where most of the pixels we had were an empty part of unused pixels.
Now these pixels are being cut off, which means that we have freed up memory for rendering, now, for example, 200x1000 pixels will be rendered.
The update is not possible. Since you recently bought the plugin, you can make a refund and purchase Camera 360 v3. Write me an your Order ID to email Lenina62-ivan@mail.ru
But please keep in mind that the plugin is currently at an early stage and I am working on its improvements. Any unexpected errors may be detected.
I also ask you to read the detailed description so that there are no misunderstandings.
Hello, English is not my native language, I communicate through translation software, I would like to consult, I am currently using 360cameraV2, I have always encountered the problem of image seam (even though I have fully followed the precautions you mentioned), I would like to ask if 360cameraV3 still has this problem?
Hi!
You can send me your scene, send me an example of the problem, and I’ll help you check it out. In general, it is usually possible to solve problems.
My Email Lenina62-ivan@mail.ru
When I render with v3, I find that it ends up with 60 fewer sequence frames. For example, when I render 0-1000, it only ends up with 940 images, and if I want to use pre-render, it ends up with negative frames. Is there a solution to this?
Hi!
Please check your project version (open uproject file and check Version Engine) and plugin version (open folder plugin and check uplugin → version engine)?
You copy plugin to project?
If need plugin for 5.3 engine, please install Plugin for 5.3 engine.
I checking, all version Plugin correct for all Engine Version.
Perhaps you added a plugin of the wrong version to the engine of another version?
