Factorio Forums

Hello

Today I ran ito a little bug with the artillery remote. I should mention that I encountered that bug while playing with mods (aka Bob's and Angels).
But I loaded that save up in my Factorio vanilla instance and the same thing happent.

So whats wrong.
Artillery Remote map markers usually expire either after a set amount of time or if a cannon has fired a shot. But currently cannonfire does not remove markers on the map leading to the following problem that all cannons in range will constanly fire on the first marker until it expires time wise (wich is a huge waste in ammunition).

So at the moment the Artillery-Remote is usless.

Can not produce, post a save with markers on map that do not expire when fired at please. I suspect that this first marker are actually several stacked on top of one another.

Here you go thats the save.

Its not just the first marker. I've made a short video to show exactly what happens on my end.
https://youtu.be/JrBJaYiB3RM
To be clear that video was made in my Factorio Vanilla instance.

Do you have map drag bound to middle mouse button or generally rebound?

There are no marker when I load your save, did you upload one without or do they not load?

I have read on other threads, bevor posting this one, that some peaple have problems with map drag and the remote tool.
But since I never changend that key specific setting I did'nt saw any similaritys.

drag map - Left mous button
Place Tag on the map - Right mouse button

the only thing I ever changed is I swaped mine and build buttons. So left mine and right build (Years of minecraft burnt that into my muscle memory).

Loewchen wrote:There are no marker when I load your save, did you upload one without or do they not load?

The first save I uploded is bevor I placed any markers at the map sorry I provide you antoher save in just a sec.

EDIT: save atached, with markers placed on the map

There are 4 target marker stacked on each position. To be sure: If you remove all mods, load a save without target marker and set target markers, you get the same issue?

Loewchen wrote:you remove all mods, load a save without target marker and set target markers, you get the same issue?

Thats what I did, as seen in the short video. I toggled all mods of and loaded that save and used the Arty remote.

Post a log and the config file please, make sure to mask passwords.

Sorry to ask. Do you mean the config.ini and the Current.log file

Animar wrote:Sorry to ask. Do you mean the config.ini and the Current.log file

Yes

Here you go.

I removed the Password from the .ini and also gave you a new save (with markers on map).

Well happy to say I found a workarround for that problem.

Since you said to me that there were several markers on top of each other it got me thinking. The remote basicly works like a paintbrush tool, you could click and hold and paint the map with markers. But for whatever reason even a single klick paints already 4 markers, so what if I could klick faster. Luckyly I have a keyboard that is able record and play makros. My theory was if could cut the actual button down time to a very low time interval. The game would only see one superfast klick.

Start;
right mouse down;
pause 0.0005 sec;
right mouse up;
pause 0.500 sec; //actually not needed just for safty
end;

And it worked. By using this makro I can place single markers on the map. But why does the game record mutliple map markers if Klick normaly with my mouse is a mystery to me. Its the same mouse I used when 0.16 was released and I had no issues with the remote tool back then.

Artillery shots time out after they have had the prototype-defined amount of shots fired at them. If a mod is messing with those values then you can get what you're getting but from the way the base game logic is setup if you click and place a marker it will exist until 1 artillery has shot at it.

If your clicking is registering 4 times per click that's on your end to fix since the game only listens to mouse clicks.

I think at least portions of this should be fixed for the next version of 0.16.

Well thanks the 16.29 update did fix my issue. I don't need to use my workaround makro any longer.
You can close this thread and mark it as solved if you want.