Hello Mr. Wihgranter,
after the installation of the latest Nvidia driver, RC is running again in the reconstruction, but now again new problems arise. In the version before 01.08.2017 ran everything without problems and I could create good ortho-projections. Since the update on 01.08.2017 new problems arise. With the old version, I was able to create ortho projections from models with over 40 million tris. Since the update always shows the Hineis on which my video memory is not enough. Orthoprojections I can not create any more synonymous if I consider the following procedure:
-> import pictures;
-> Import and assign GroundControlPoints;
-> Execute Aligment;
-> Generate Preview;
-> use the clipping function to select a facade section;
-> perform the reconstruction;
-> Simplify the model down to 38 million tris;
-> push the texture;
-> perform the ortho projection.
For the results, see Appendix.
Why is everything now so complicated, if it was much easier before.
Question: How do I get back to the previous version before 01.08.2017 where everything worked. The support is miserable since I always give in the Crashreport an additional hint and ask a question. To date, I have not received an answer yet!
So working with RC makes no sense. Dates of ongoing customer projects can no longer be adhered to since the update. The rise in time is increasing and it still does not work.
Is there no reasonable solution or a support which also works?
In the old version there were not all these problems! Basically I can not use RC for my customer projects since the update!
Is there a solution to the new problems?
PS. A complete workflow for the new version would be helpful as the old workflow does not work anymore!
I never experienced this because I usually simplify significantly before texturing and creating orthophotos.
But I did manage to create some from 700M+ models that were UNtextured.
Does that work for you or does it also crash?
It might help to pinpoint the bug…
I’m lso having issues with exported orthos not being in the project coordinate system.
RealityCapture version 1.0.2.3008 RC
Here is an image showing the Application Settings coordinate system:
this one shows the control point coordinate system (same as application settings):
this one shows that the component is geo-referenced:
This one shows the settings for the Ortho Projection Tool:
In the help documentation is says to use top if exporting to GIS. I also created orthos using Map and Arbitrary and exported to compare world files. The world file is the same for all 3.
This shows the export ortho projection options:
I have tried with projected, global, and image. The results are the same.
This image shows that the coordinate read out for the cursor location on the ortho has the same coordinates for the UTM projection as it does for the GPS coordinates:
The UTM coordinates should be more like this: N3491092.692; E667175.913.
Even though the Ortho Projection Tool indicated the Coordinate system as epsg:32636 - WGS 84 / UTM zone 36N, I open the Coordinate System dialog and scrolled down the list to epsg:32636 - WGS 84 / UTM zone 36N and selected it. When I did the coordinates for Centre updated to proper UTM coordinates. I rendered a new ortho and it exported correctly. This image shows the results of re-selecting the Coordinate system:
You can see the coordinate read out for the cursor location on the ortho is also correct now.
It is pretty much working now. There is only one small issue. Sometimes the exported ortho is shifted slightly. This can be resolved by changing the pixel size and re-rendering and exporting the new ortho. There is more info on this towards the bottom of this thread: