V15.0beta1 dated 20130905 may be patched as described in #156.
Still problem with extensions (built-in-modules).
GEM Module/Extension for V15 available;
any ideas about implementation?
Karl
karl
Following this forum link over the next few weeks may help.
I guess we will have to wait for all the fine details to emerge.Code:Please Login or Register to see the links
V15.0beta1 dated 20130905 may be patched as described in #156.
Still problem with extensions (built-in-modules).
GEM Module/Extension for V15 available;
any ideas about implementation?
Karl
Last edited by Neil; 13th September 2013 at 11:49 PM. Reason: Merged 2 consecutive posts.
V15.0 dated 20130919 released; may also be patched as described in #156.
Still problem with extensions (built-in-modules).
GEM/Lidar/OTF Module/Extensions for V15 available;
any ideas about implementation?
Karl
I agree.
I have tested 32-bit version for 2 days now. Patch is working correctly and activates all 3 modules.
I have tested 1 module; is working.
GREAT!!!!!!
Last edited by Boki; 9th October 2019 at 08:31 AM.
Thx Arturo for the 15 patch, works great.
Any news/hints on a fix for the non-DPI capable patcher? It's cumbersome having to reset Windows to useless "100%" dpi, log out, log in, patch, restore Optimal DPI %, log out, log in... only to patch a few binary files...
I checked the 15.0.5 from [Only registered and activated users can see links. ], was not aware of the thread here.
The keygen is from the same group I would say from the above screenshots.
But since it is reported at virustotal with quite a few hits I only used the patcher in a sandbox and only used the 64bit version.
Maybe using a sandbox for the patcher would help in your cases too.
Data download from the supported online sources works fine, at least for the free ones.
Only downside is that some are quite limited in terms of the download speed, making downloads for big areas quite painful.
By big I mean not a national park, but state size...
Export of 3D PDF's is untested as I have no GPS to test them with, might have to look into that one day...
Last edited by Downunder35m; 28th October 2013 at 05:09 PM.
Password for all my files: downunder
I did some more tests with this patcher and seems the problem is not the patching itself,
but the way the patcher is programmed.
Seems to be a "quick and dirty" job, which might even explain the malware warnings as the code packer used seems to be infected.
(not a professional in this stuff)
When it starts it uses a few Windows functions and calls, again not programmed in the best way possible...
All paths are fixed as I was unable to patch if the program folder differs from what the setup suggested or if the setup files are unpacked manually to get to the EXE file.
I got the stuff working for both the 64 and 32bit version by using a sandbox and with same results by running the patcher directly from the install folder - but onlyif the paths had not been changed during setup.
Password for all my files: downunder
Bookmarks