nesias

Oh boy... sounds like he is a real "nice" guy.

My guess is, that that person is nothing more than a troll.

Well that was fast, if i find some more of them i will post a list here. Thanks for the update btw.

I found some missing commands that are listed Here but are not highlighted in Notepadd++: lnbSetPictureRight lnbSetPictureColor lnbSetPictureColorRight lnbSetPictureColorSelected lnbSetPictureColorSelectedRight That is not a complete list, but i can confirm that these commands exist, work and get recognized by the debug console (including info Popups). (And yes these are probably only used in very rare cases.) P.S. also it looks like some of the 1.76 commands are missing too (allAirports, drawTriangle, selectRandomWeighted).

oh okay, i just noticed the fix mention in the dev changelog and wanted to try if that may have fixed the k variant

I just tested some stuff in Dev Branch and it looks like that there is an engine bug that crippels laser guided weapons (see Dev Branch Changelog). While im not able to use the Hellfire K Variant in Stable (acts like a dumbfire), its functions fine in Dev. It will follow a laser look just as it is supposed to do (as far as i know), and can be guided that way. While i did not check the L Variant in Dev it seems fine in Stable (using active radar for locking).

Any chance for a fix today ? Or is that up to Steam?

I have the same problem, looks like the menu isn't scaling correct with the UI size setting.

@torndeco Just downloaded Version 1.025, but it seems like you didn't include the extDB3.pbo file ? Also, do you have any plans to include support for the alternative syntax of callExtension ? It looks very similar to what you showed in October.

@Torndeco You may wanna check "9:LOCK:<code>" cause im able to Unlock with it if i use the correct code. This happens in 1.007 and maybe started atleast somewhere around 1.004 if not right after the UNLOCK fix. Logfile (a bit shortend) created with Debug.dll: (Sorry for not posting this on Bitbucket i will try to post issues over there in future.)

That is more or less what it should be (keep in mind that this is extremly depending on how precise that script tracks the shoreline).

EDIT: Okay i do have an idea why it happens. (Still Version 1.001) [07:19:08:134360 +02:00] [Thread 8120] extDB3: Input from Server: 9:VERSION [07:19:08:134360 +02:00] [Thread 8120] extDB3: Output to Server: 1.001 [07:19:33:476809 +02:00] [Thread 8120] extDB3: Input from Server: 9:VERSION [07:19:33:476809 +02:00] [Thread 8120] extDB3: Output to Server: 1.001 [07:19:38:576101 +02:00] [Thread 8120] extDB3: Input from Server: 9:LOCK_STATUS [07:19:38:576101 +02:00] [Thread 8120] extDB3: Output to Server: [0] [07:19:38:577101 +02:00] [Thread 8120] extDB3: Input from Server: 9:ADD_DATABASE:DB_1:DB_A [07:19:38:582101 +02:00] [Thread 8120] extDB3: Output to Server: [07:19:38:582101 +02:00] [Thread 8120] extDB3: Input from Server: 9:ADD_DATABASE_PROTOCOL:DB_A:SQL:SQL_A:TEXT [07:19:38:582101 +02:00] [Thread 8120] extDB3: SQL: Initialized: Add Quotes around TEXT Datatypes: true [07:19:38:582101 +02:00] [Thread 8120] extDB3: SQL: Initialized: NULL = "" [07:19:38:582101 +02:00] [Thread 8120] extDB3: Output to Server: [1] [07:20:11:527986 +02:00] [Thread 8120] extDB3: Input from Server: 2:SQL_A:SELECT * FROM market_test.storage; [07:20:11:527986 +02:00] [Thread 8120] extDB3: Output to Server: [2,"100"] [07:20:11:527986 +02:00] [Thread 2984] extDB3: SQL: Trace: Input: SELECT * FROM market_test.storage; [07:20:11:528986 +02:00] [Thread 2984] extDB3: SQL: Trace: Result: [1,[[1,"oil",1000,10,10000,"playera","001"],[2,"beton",10,1,10,"playerb","001"]]] [07:20:19:155422 +02:00] [Thread 8120] extDB3: Input from Server: 4:100 [07:20:19:155422 +02:00] [Thread 8120] extDB3: Output to Server: [1,[[1,"oil",1000,10,10000,"playera","001"],[2,"beton",10,1,10,"playerb","001"]]] [07:21:00:654795 +02:00] [Thread 8120] extDB3: Input from Server: 9:RESET [07:21:00:695798 +02:00] [Thread 8120] extDB3: Output to Server: [1] [07:21:05:135052 +02:00] [Thread 8120] extDB3: Input from Server: 9:LOCK_STATUS [07:21:05:135052 +02:00] [Thread 8120] extDB3: Output to Server: [0] [07:21:05:135052 +02:00] [Thread 8120] extDB3: Input from Server: 9:ADD_DATABASE:DB_1:DB_A [07:21:05:136052 +02:00] [Thread 8120] extDB3: Output to Server: [07:21:05:136052 +02:00] [Thread 8120] extDB3: Input from Server: 9:ADD_DATABASE_PROTOCOL:DB_A:SQL:SQL_A:TEXT [07:21:05:136052 +02:00] [Thread 8120] extDB3: SQL: Initialized: Add Quotes around TEXT Datatypes: true [07:21:05:136052 +02:00] [Thread 8120] extDB3: SQL: Initialized: NULL = "" [07:21:05:136052 +02:00] [Thread 8120] extDB3: Output to Server: [1] [07:21:09:802319 +02:00] [Thread 8120] extDB3: Input from Server: SELECT * FROM market_test.storage; [07:21:09:802319 +02:00] [Thread 8120] extDB3: Error Invalid Message: SELECT * FROM market_test.storage; [07:21:09:802319 +02:00] [Thread 8120] extDB3: Output to Server: [0,"Error Invalid Message"] [07:21:18:087793 +02:00] [Thread 8120] extDB3: Input from Server: 2:SQL_A:SELECT * FROM market_test.storage; [07:21:18:087793 +02:00] [Thread 8120] extDB3: Output to Server: [2,"101"] [07:21:23:292090 +02:00] [Thread 8120] extDB3: Input from Server: 4:101 [07:21:23:292090 +02:00] [Thread 8120] extDB3: Output to Server: [3] [07:21:30:363495 +02:00] [Thread 8120] extDB3: Input from Server: 4:101 [07:21:30:363495 +02:00] [Thread 8120] extDB3: Output to Server: [3] [07:21:31:036533 +02:00] [Thread 8120] extDB3: Input from Server: 4:101 [07:21:31:036533 +02:00] [Thread 8120] extDB3: Output to Server: [3] [07:26:48:265678 +02:00] [Thread 8120] extDB3: Input from Server: 2:SQL_A:SELECT * FROM market_test.storage; [07:26:48:265678 +02:00] [Thread 8120] extDB3: Output to Server: [2,"102"] [07:26:54:258020 +02:00] [Thread 8120] extDB3: Input from Server: 4:102 [07:26:54:258020 +02:00] [Thread 8120] extDB3: Output to Server: [3] [07:26:56:072124 +02:00] [Thread 8120] extDB3: Input from Server: 4:102 [07:26:56:072124 +02:00] [Thread 8120] extDB3: Output to Server: [3] [07:26:57:152186 +02:00] [Thread 8120] extDB3: Input from Server: 4:102 [07:26:57:152186 +02:00] [Thread 8120] extDB3: Output to Server: [3] Looks like RESET is somehow causing it. I have a test map for a script and at the end of each test run i used RESET before switching back to Editor so the next time my Init script won't throw an error. EDIT: I have tested it with the v1.002 Debug dll and it is still happening after RESET. Using a script which will try to get any data out resulted in an +20k line big log file with no result except [3].

Okay, looks like i have 2 or 3 Bugs. ExtDB3 Version is 1.001. First one: I can't get UNLOCK to work, everytime i try to unlock using a code (empty "9:UNLOCK:", correct code or wrong code) i get an empty string as return and its still locked. All tries without a code (just "9:UNLOCK") will return an error message (as it should). Second one: Every time i try to retrieve a message using the "4:<ID>" methode i only get "[3]" as answer, im not sure if this is a bug or if something is wrong on my side. If somebody else encounters this, please say so. (Protocol is SQL) Third one: There is no message if i try to use ADD_DATABASE with a non existing or existing config entry. I only get a message if the DB is already connected. @torndeco One question, would you prefer to get these bug reports here or should we use the issue function of bitbucket?

@torndeco thanks for releasing extdb3, but it looks like i already found a bug. When calling extdb3 and retrieving data from a table, you need to add a " ] " to the answer string befor you can call compile it. using sqf code like this: "extDB3" callExtension "0:SQL1:SELECT * FROM test" gets this return: "[1,[[1,["testa", 1]],[2,["testb", 2]]]" which probably should be: "[1,[[1,["testa", 1]],[2,["testb", 2]]]]" This bug happens before and after LOCK, but not if i use something like "9:LOCK" ("9:LOCAL_TIME" works fine). Database Protocoll is "SQL" (SQL_Raw throws a unkown protocol error). Database Server is MySQL 5.7.11 Win64 (x86_64) (Community Version). Arma 3 Version is 1.58.135742 . OS is Win7 64bit. Only Mod used is extDB3. Battleeye is switched off. p.s.: I almost forgot another one, after starting arma i got a little popup saying "Script \system\fn_preInit.sqf not found". So far i can confirm that the file is included in the .pbo and there is an empty entry in "Functions Viewer", but Arma can't find it.