WrapX argument request

Feature Requests
1

hey guys,

I wrote some python scripts to automate batch process of a lot of blendshapes, I have to do texture transfer between high poly meshes.

the problem is that with high polycount / high texture resolution, wrapX tends to crash few times during the process.

I wrote a recursive python loop (out of wrapX) that lauch wrapX texture transfert, then it check that all the textures have been processed, if not (crashed), it launch wrapX texture transfert again and again until all textures are done.

It’s working well, the only problem is the “send crash report dialog” that requires user to interact each time wrapX restarts.

It would be awesome to have a flag to desactivate the “send crash report” dialog, or maybe to automatically send it.

Thanks :slight_smile:

2

Hello Paul!

Short answer:

After crashing you can write any string (even empty) to log file in “C:\Documents and Settings\USERNAME\AppData\Local\R3DS\WrapX\WrapX.log” and “send logs” dialog will not appear next time.

Details:

When WrapX crashes, it creates a minidump crash file (dmp) in directory “C:\Documents and Settings\USERNAME\AppData\Local\R3DS\WrapX”
This file is prefixed with PID of crashed process. When WrapX starts it reads log file. Log lines are in format “Date PID message”. WrapX checks if there is a crash dump file prefixed with PID from last line and shows dialog if such file exists. So adding any line which does not contain last PID will be interpreted as “no crash last time”.

We fixed some bugs related to crashes while texture transfer, so I recommend you to use newest pre-release WrapX version:
http://russian3dscanner.com/downloads/Paul/R3DS-WrapX-1.2.0-64-Bit.zip

Since last time you requested WrapX with console window, in archive you can find two versions of binary - usual WrapX.exe and WrapX_console.exe.

3

Hey Paul,

I hope previous post will solve the problem.

Let me add my two cents: I’m not sure if it works for you but if you use Photoscan for scanning, i would highly recommend to export wrapped model back to Photoscan and generate texture from original photos, which might lead to much better quality.

http://www.russian3dscanner.com/images/TextureProjectionExample.jpg

Thank you again for great feedback!

4

Thanks a lot for answer :slight_smile: that’s pretty clear,

reprojecting textures in agisoft is smarter, but i found WrapX easier to automate, and the results are still pretty good.

console is a great feature ! :slight_smile:

Thx for this nice piece of software :wink:

Paul.

5

Hi,

that’s great to know there’s console version of WrapX.
As a customer of wrap, where can I download it? Is it a non-Gui version of WrapX 1.3.x?

thanks

6

Hi viper_0711!

Console version discussed in this thread is not non-gui, it’s just usual WrapX which creates console window right after start in which you can see all debug messages instantly.

Non-gui version of WrapX will be a standalone python module. We are working on it. It’s not ready yet for public release but if you need it then I can send you in some days a beta-version which can be also used.

Right now some automation can be achieved by passing command line arguments to WrapX while starting. I just wrote documentation page about it: http://www.russian3dscanner.com/docs/WrapX/wrapConsole.html

Ivan

7

I have waited a long time, when will be available for sale