Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Petr Ga]

Hi,
I try to use quickfort, but output is messy - design is different from what i expect, looks like random click

Final output: d{Enter}%6666{Enter}%4441d{Enter}%6666{Enter}%4441d{Enter}%6666{Enter}%4441d{Enter}%6666{Enter}%4441d{Enter}%6666{Enter}%7777

Strange; I ran your sample .csv and it worked for me; it also produced identical final output as what you included in your post.

What OS & DF version are you running?

Try this:
1. Try typing the sequence of keys in "Final output" manually into DF (ignoring % chars and hitting Enter for {Enter}) -- does it dig properly?
2. Assuming #1 worked, try editing your options.txt:
    (a) Set DelayMultiplier=10, KeyPressDuration=10; save and retest
    (b) Additionally set SendMode=SendPlay;save and retest
    (c) Set SendMode to each of the other options (Send, SendEvent, SendInput); save and retest

Most likely one of those options changes should make things work for you.

output looks like this - all moves are like with shift (5 line 41 square in length, 10 square in distance):


i tried all options. I have default interface.txdst except for secondary scroll - i use alt+2,4,6,8 (laptop here)

[joelpt]

Interesting. I'm thinking your Alt+Num assignments may actually be the cause, since you have to press Alt+D to start QF playback. It may be thinking that the Alt key is being held down for the duration of playback (DF seeing the Alt-keydown event but not the Alt-keyup).

Try temporarily disabling those Alt+Num assignments in your interface.txt and see if the problem goes away. If it does, I think I probably have a solution that I could implement within QF which would allow using Alt+Num to work without issue.

[Petr Ga]

sorry, no luck with standard plus minus divide keys, output is still the same.

i ran vanilla df 31.03 and vanilla quickfort. also with tips for options.txt, no success.

see here:
http://mkv25.net/dfma/movie-2127-quickfort111incorrectbehaviour

[joelpt]

sorry, no luck with standard plus minus divide keys, output is still the same.

i ran vanilla df 31.03 and vanilla quickfort. also with tips for options.txt, no success.

see here:
http://mkv25.net/dfma/movie-2127-quickfort111incorrectbehaviour

Very strange. Well, I'll keep thinking about what else could be involved. I'll try running with Czech locale here and see if I can reproduce the problem.  It is definitely acting like the shift key is being held down with the movement keys.

One more thing you could try is changing the KeyLeft, KeyRight, etc. settings in options.txt to use the arrow keys, for example 'KeyRight={Right}'. And set UseDiagonalMoveKeys=0. Maybe that'll circumvent the problem, maybe not.

[Petr Ga]

sorry, no luck with standard plus minus divide keys, output is still the same.

i ran vanilla df 31.03 and vanilla quickfort. also with tips for options.txt, no success.

see here:
http://mkv25.net/dfma/movie-2127-quickfort111incorrectbehaviour

Very strange. Well, I'll keep thinking about what else could be involved. I'll try running with Czech locale here and see if I can reproduce the problem.  It is definitely acting like the shift key is being held down with the movement keys.

One more thing you could try is changing the KeyLeft, KeyRight, etc. settings in options.txt to use the arrow keys, for example 'KeyRight={Right}'. And set UseDiagonalMoveKeys=0. Maybe that'll circumvent the problem, maybe not.

Haleluja!
I can confirm it works!

Modifications:
vanilla quickfort 1.11 folder
open options.txt
change

KeyLeft = 4
KeyRight = 6
KeyUp = 8
KeyDown = 2

UseDiagonalMoveKeys = 1

for

KeyLeft = {Left}
KeyRight = {Right}
KeyUp = {Up}
KeyDown = {Down}

UseDiagonalMoveKeys = 0


now, what are equivalent for 7 9 1 3? {LeftUp} etc?

it is rather slow, but - IT WORKS!!

[joelpt]

Haleluja!
I can confirm it works!

now, what are equivalent for 7 9 1 3? {LeftUp} etc?

I don't think there are any alternatives. Maybe you could set those up in interface.txt to match something that works on your system.

[joelpt]

I've been working on a rewrite of the core designation algorithm for Quickfort and am nearing release for Quickfort 2.00.

The new version uses a new core algorithm written in Python, and continues to use AutoHotKey for the GUI/hotkey aspects.

Here's a comparison video showing the performance difference between QF 1.11 and 2.00-pre.

Quickfort 1.11 vs 2.00-pre performance


Left to implement: build modes other than "dig"; multilayer support; keystroke transformation (for use with DF macros later); repeat mode; and a few loose ends.

[Draco18s]

That's awesome, and I was about to ask the stupid question of, "have you finally made it so it does the even lines in reverse?"

(eg:

step 1:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ->

step 2:
<-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

rather than doing a carriage return line feed)

[tastypaste]

Wow, QF 2.0 looks great.

[Gabriel A. Zorrilla]

Linux version?

[Ratbert_CP]

Linux version?

I don't know about QF itself being ported, but you'll need something like IronAHK running on Mono to actually process the resulting scripts.

[Sulphuratum]

a little question before i download it: how to control the material from which are the constructed walls made?
uhh 2nd one:and do constructed floors work?

it would help my aboveground forts, designating is exhausting as hell

[palsch]

Because the materials are in an arbitrary order (distance from the point) each time you assign something, there is no way to consistently automatically pick the same material. Instead it just uses the first one in the list every time.

You can game it by forbidding all other materials in the stock menu or by making sure a sizeable stockpile of the required material is always closest to your build site. Other than that... nope.

[Heavenfall]

Thanks for making this, helps so much with some very tedious tasks.

Also, looking forward to 2.0 

[Aklyon]

Does this work with .31.08?