It used to be that shift-open on launch would bring up a confirmation window, not seeing that for some while now. Thanks for addressing when is good.
Hello Benjamin,
what version of RealityCapture do you use? I tried it with version 1.0.3.3939 and it is working correctly.
I’m up to date, 1.0.3.3939. Thank you.
Benjy
Hello Benjy,
do you use some remote control for a PC on which you use RC?
Can you please try to use On-screen keyboard, press Shift and try to launch application like this?
I’m confused. I use TeamViewer from time to time on the same PC with RC. Are you wanting me to use the on-screen keyboard from a different machine remoting in to try the Shift-open to launch? I’m pretty sure the shift button on my keyboard isn’t malfunctioning, caps are working.
While we’re at it, I’m seeing more weirdnesses (the inability to reset workflow settings persisting), now getting unexpected results with the following alignment settings. With Force component rematch set to True and Merge components only to True, and considering I have a single component going in, I’m getting a kazillion components. Also, another weirdness, what had me needing to run alignment on a project with a single component already optimized, I tried exporting a portion of the 1176-image component (see active and inactive cameras in attached image), got the red screen error saying a particular image used in registration wasn’t available. To note, all images are set to “Use all image features”, know that can be an issue if the settings are mixed among the set in the active component.
Thanks for your help.
Benjy
hello, the issue has been fixed and the fix will come out with the next release soon
That’s good to hear. Any thoughts on the other troubles I posted here, or should I post in a separate thread? Thanks.
Hello Benjamin,
I meant that there can be problem with sending the keyboard shortcuts when using remote control. Therefore I suggested that you could try to use on-screen keyboard to launch the application along with the pressed Shift key to rule out the problem with the keyboard.
Regarding to your second problem, use ‘Merge components only’ only in cases when you have several components and you wish to join only these components together and you do not need to add cameras that were not aligned. With this setting set to true no new cameras will be aligned.
‘Force component rematch’ set to true uses previously calculated camera poses and tries to find new matches. Application will realign the cameras among eacth other. In this case we recommend to keep only the components with more cameras aligned (bigger components) and delete the components with almost no images aligned.
We will prepare a tutorial with a detailed description of the alignment settings.
Can you please post a screenshot of the red error message? Have you moved or renamed any images?
Zuzana Ďuríčková said:
“In this case we recommend to keep only the components with more cameras aligned (bigger components) and delete the components with almost no images aligned.”
I expect there’s a logic to that recommendation, which would illuminate a bit how RC works - so can you say why that recommendation?
Zuzana,
I see Lubenko says this is now a known issue with the settings not being reset, that a new version is coming out to address this issue. I so wish your team could add to the list something minor, in terms of dev, but a huge pain for user, also previously acknowledged as a known issue, preference to use Project folder as Cache location isn’t working. Using same cache location between project is a problem multiplier. Thanks for passing along.
About the red error message, here it is:
I had previously run into this issue when a) photos being referenced in exported registration had different input values, e.g. Use all image features, or b) if a registration was being exported from an older component when a younger component with altered tie points was present. Note, I got this red flag with neither condition and only had a single component in the project.
About your distinctions between Merge components only, my understanding was this setting is benign to preserving an existing component. It may not get merged with another component, but whatever that result is, the only thing affecting whether a component is preserved or is allowed to split is the Merge components only setting. That previous screen shot I posted with all the smaller components was meant to show (though I can see the settings don’t quite make this clear) that I only had one component in this project, had it set to Merge component only, then ran alignment and got all the splintering, quite unexpected. So, I have compounded problems, can’t export and can’t align again without the splintering. Is my project possibly corrupt?
Thanks.
Update, in a new project I imported a component and about 900 images, the combination belonging to what was the unified component I was unable to export (red flag) and was then unable to align, as described in my previous post. So, in this new project I saved and cleared cache, set Merge components only to False and Force component rematch to True. With the cache cleared, I would expect to see a slow moving progress bar, as feature detection would have to begin from scratch. Instead, I saw the progress bar jump to about a third done, is this RC affirming it sees all the poses contained in the imported component?. Then about 30 seconds later the progress bar races through to completion, leaving a new instance of this imported component. As I can’t reset workflow settings, I forget what the default is in a new project. Does Force component rematch default to True or False? If True, then this behavior seems abnormal. If False, then this informs me to be extra deliberate in pulling this trigger.
Can’t reset workflow settings? sounds like you have a deeply wounded installation - how scary - re-install makes no difference?
Mine resets fine (by the button bottom left of Alignment settings in 1Ds) and I can confirm that Force rematch and Marge components should both reset to False.
Thanks, Tom. A “wounded installation”, boy, hits the nail on the thumb. That would explain all the other weirdnesses, e.g. splitting of components with both Force component rematch and Merge components only set to True, inability to export registration, other combinations of alignment settings and odd behavior. So, with a re-install making no difference, which I’ve done and can verify, how is that dealt with? Did you encounter this yourself or just read about it?
Thanks!
Benjy
For me, Shift+Open button ignores the Shift and simply does Open - unimportant as I’ve always used the Reset button bottom left of Alignment settings in 1Ds, which works fine. So at least, hopefully, you can Reset?
But that’s the least of your problems, which I haven’t tested. Has RC acknowledged the rest, fix coming soon?
I’m not seeing a reset button in the Alignment settings. Can you please send me a screen grab of that dialog? I see one in the Workflow settings, but that’s not resetting everything, noticed a change to the layout, maybe something else got changed, but see Alignment settings and other Workflow settings remained the same. RC didn’t indicate a fix, Lubenko simply said a fix was coming in the next update.
Thanks.
Top button of three at bottom left
Oh, saw those tiny icons, but have glossed over them. I see the Workflow settings also features the reset icon, have now used both, so we’ll see if that makes any difference. Thanks.