xbelanch

IT WORKS! I opened the heightmap with L3DT and set a lower value (-10) to a smallest zone of the terrain and now it crunch without any issues. Thanks so much @HorribleGoat!

Better a picture rather than words: https://imgur.com/a/hqmxLiG As you can see, it's not flat... but it's not an island (no water)

Well, I reinstalled Arma 3 Tools, mounted P drive as PCM explains and follow the rest of the terrain tutorial step by step (only I changed the tag and project name)... and I'm still stuck with the same error: MakePbo x64UnicodeVersion 1.99, Dll 7.16 "icgc_collserola_terrain" -PsgW -X=*.psd,*.psb,*.bat,*.rar,*.7z,thumbs.db,*.txt,*.h,*.dep,*.cpp,*.bak,*.tga,*.png,*.log,*.pew,*.hpp,source -@=icgc\icgc_collserola_terrain p:\temp\icgc\icgc_collserola_terrain 808464432 huh Pbo can't read wrp makepbo failed icgc_collserola_terrain.pbo not produced due to error(s) Job(s) completed in 76secs on Tue Aug 13 21:32:32 2019 That's driving me mad...

Thanks for the help @RoF I was using both Arma Tools launcher and Mikero Tools... certainly that's a mess. I think it's better start from the scratch...

Well, it doesnt make sense... At the moment I found a workaround for this issue: unmount the p drive and mount it again... maybe the root of the problem is related to .wrp file permissions.

I got the same error :( Any clue or suggestion? @LeLapinDeCombat

For a personal project, I need some help to emulate something like that: Any suggestion of documentation, tutorials, resources, source code or whatever you think it helps me to develop that? Thanks in advance

My bad. I was launching Arma the whole time directly from the exe not from the launcher... lesson learned and sorry for wasting your time :(

Color me embarassed. Well... what can I say? Good news? It works. Bad news? It was because BE :( My apologies... I've lost the general picture shrinking my mind on the dll compilation output. Anyway... very thanks for helping me. :) Now we can say that Mingw can build extensions for Arma 3

Yep. MSVC built is fully working without no problem with BE... I started to think that the problem with Mingw dll is related to .CRT (http://stackoverflow.com/questions/15822048/using-mingw-to-build-a-windows-dll-that-depends-on-visual-studio-crt-msvcr110-d)

Yep, alright... "dinamically" wasn't correct. I understand (and sorry in advance if I'm wrong) when you say "loads the dll on first" it refers at the time that any sqf calls the function callExtension. Before that Arma doesn't load any third-party dlls (and this makes sense for safety reasons I guess) and following that logic you can put a new dll while Arma is running and load it (always at your own risk xD)

No... Arma doesn't load it. I checked it with Process Explorer. Arma loads the dlls (as you said) dinamically every time you use callExtension (and that works if I check it with a dll built with VS). Maybe I must open a ticket at https://feedback.bistudio.com/?

test.cpp source code: #include <Windows.h> #include <string.h> extern "C" __declspec(dllexport) void __stdcall RVExtension(char *output, int outputSize, const char *function) { outputSize -= 1; if (!strcmp(function,"version")) { strncpy(output,"1.0",outputSize); } else if (strcmp(function, "function") == 0) { strncpy(output, "return of a function", outputSize); } else { strncpy(output,function,outputSize); } } // Normal Windows DLL junk... BOOL APIENTRY DllMain(HMODULE hModule, DWORD ul_reason_for_call, LPVOID lpReserved ) { switch (ul_reason_for_call) { case DLL_PROCESS_ATTACH: break; case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: case DLL_PROCESS_DETACH: break; } return TRUE; } compilation command lines: gcc -W -c -o test.o test.cpp && dllwrap -s -o test.dll --def test.def test.o -Wl,--subsystem -Wl,windows -Wl,--enable-stdcall-fixup where test.def is: EXPORTS _RVExtension@12 = RVExtension if I execute your helpful testing code it works: $ ./foxyy.exe result:1.0 same source code compiled with VS CL I obtain the same result: cl /LD test.cpp /link /out:test2.dll Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86 Copyright (C) Microsoft Corporation. All rights reserved. test.cpp Microsoft (R) Incremental Linker Version 10.00.40219.01 Copyright (C) Microsoft Corporation. All rights reserved. /out:test.dll /dll /implib:test.lib /out:test2.dll test.obj Creating library test.lib and object test.exp Dumpbin /exports of the binary generated with g++: File Type: DLL Section contains the following exports for test.dll 00000000 characteristics 579F5C22 time date stamp Mon Aug 01 16:26:42 2016 0.00 version 1 ordinal base 1 number of functions 1 number of names ordinal hint RVA name 1 0 00001570 _RVExtension@12 Summary 1000 .CRT 1000 .bss 1000 .data 1000 .edata 1000 .eh_fram 1000 .idata 1000 .rdata 1000 .reloc 1000 .rsrc 2000 .text 1000 .tls

Ouch! alright... but that's the compiler do :-/ it seems to be closed to this thread: http://stackoverflow.com/questions/35701657/how-to-implement-the-rvextension-function-for-an-arma-3-dll-in-rust UPDATE: This http://stackoverflow.com/questions/2804893/c-dll-export-decorated-mangled-names, this http://stackoverflow.com/questions/2810118/how-to-tell-the-mingw-linker-not-to-export-all-symbols and this http://www.transmissionzero.co.uk/computing/advanced-mingw-dll-topics/ helped me a lot to understand much better the challenge. After spending several hours dealing with it I achieved the same symbol name that exports Visual Studio but still doesn't work uu

Hi Foxyy. Yep. It does, but it doesn't work. Here's the output after compiling with next g++ parameters: g++ -shared -fPIC -m32 -std=c++11 test.cpp -o test.dll -Wl,--subsystem -Wl,windows -Wl,--out-implib=libtest.dll.a -Wl,--export-all-symbols -Wl,--enable-auto-import If I test the result with file test.dll it results: test.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows and here's the result after execute dumpbin /exports test.dll Dump of file test.dll File Type: DLL Section contains the following exports for test.dll 00000000 characteristics 579E0DA9 time date stamp Sun Jul 31 16:39:37 2016 0.00 version 1 ordinal base 1 number of functions 1 number of names ordinal hint RVA name 1 0 00001570 RVExtension@12 Summary 1000 .CRT 1000 .bss 1000 .data 2000 .debug_abbrev 1000 .debug_aranges 7000 .debug_info 2000 .debug_line 1000 .debug_loc 1000 .debug_ranges 1000 .debug_str 1000 .edata 1000 .eh_frame 1000 .idata 1000 .rdata 1000 .reloc 2000 .text 1000 .tls I don't have a big experience with .dlls but it seems that .dlls built with mingw doesn't like to Arma 3 ;) It'd be great if it works... hope you have more luck and skills than me! PS: the same file compiled by cl /LD test.cpp /link /out:test.dll File Type: DLL Section contains the following exports for testMSVC.dll 00000000 characteristics 579E0EA6 time date stamp Sun Jul 31 16:43:50 2016 0.00 version 1 ordinal base 1 number of functions 1 number of names ordinal hint RVA name 1 0 00001000 _RVExtension@12 Summary 2000 .data 2000 .rdata 1000 .reloc 5000 .text