Work Width not correct. km/miles problem ? #128

Resandise · 2021-12-26T14:56:42Z

When generating course for Krone Big X 1180 with X-Collect 900-3, when I set the Work Width in CP to the work width that the shop says for the X-Collect of 9 m, the course generates too big. (First 3 screenshots)

In order to get a course that works, I have to set the work width in CP to 5.6 m.

Looking in the log, when I set the width to 9 m, when generating course, it generates at 14.5 m, but when it is set to 5.6 m, it say it generating at 9 m.

Log when set to 9 m

2021-12-26 08:41 ####### COURSE GENERATOR START ##########################################################
2021-12-26 08:41 Headland mode normal, number of passes 2, center mode up/down, min headland turn angle 60.0
2021-12-26 08:41 Width 14.5, headland first true, clockwise true. Skip rows 0
2021-12-26 08:41 Generating headland track with offset 7.25, clockwise true, inward true
2021-12-26 08:41 Generated headland track #1, area 14574, clockwise = true
2021-12-26 08:41 Generating headland track with offset 13.48, clockwise true, inward true
2021-12-26 08:41 Generated headland track #2, area 8654, clockwise = true
2021-12-26 08:41 Added 102 (of 103) waypoints to headland 1 (add straight section), starting at 3
2021-12-26 08:41 Added 0 waypoints to reach a straight section for the headland 1 lane change after 5.0 m, r = 1032226973291366.8
2021-12-26 08:41 Linked headland track 1 to next track, heading 29.9, distance 21.7, inwardAngle = 60
2021-12-26 08:41 Added 81 (of 184) waypoints to headland 2 (add full round), starting at 4
2021-12-26 08:41 Added 81 (of 265) waypoints to headland 2 (add straight section), starting at 85
2021-12-26 08:41 ROW ANGLE: FINDING THE OPTIMUM ANGLE
2021-12-26 08:41 Best angle=0, nBlocks=1, nTracks=5, smallBlockScore=0, score=15.0
2021-12-26 08:41 Block 1 has 5 tracks
2021-12-26 08:41 Generated 5 tracks for this block
2021-12-26 08:41 generation 2 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 3 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 4 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 5 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 6 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 7 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 8 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 9 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 generation 10 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 1(4)- f = 247.9, d = 40.3 m
2021-12-26 08:41 Connecting track to block 1 has 8 points
2021-12-26 08:41 1. block 1, entry corner 4, direction to next = 1, on the bottom = false, on the left = true
2021-12-26 08:41 ####### COURSE GENERATOR END ###########################################################

Log when set to 5.6 m

2021-12-26 08:48 ####### COURSE GENERATOR START ##########################################################
2021-12-26 08:48 Headland mode normal, number of passes 2, center mode up/down, min headland turn angle 60.0
2021-12-26 08:48 Width 9.0, headland first true, clockwise true. Skip rows 0
2021-12-26 08:48 Generating headland track with offset 4.50, clockwise true, inward true
2021-12-26 08:48 Generated headland track #1, area 15963, clockwise = true
2021-12-26 08:48 Generating headland track with offset 8.37, clockwise true, inward true
2021-12-26 08:48 Generated headland track #2, area 11925, clockwise = true
2021-12-26 08:48 Added 106 (of 107) waypoints to headland 1 (add straight section), starting at 4
2021-12-26 08:48 Added 0 waypoints to reach a straight section for the headland 1 lane change after 5.0 m, r = inf
2021-12-26 08:48 Linked headland track 1 to next track, heading 29.9, distance 13.5, inwardAngle = 60
2021-12-26 08:48 Added 92 (of 199) waypoints to headland 2 (add full round), starting at 4
2021-12-26 08:48 Added 92 (of 291) waypoints to headland 2 (add straight section), starting at 96
2021-12-26 08:48 ROW ANGLE: FINDING THE OPTIMUM ANGLE
2021-12-26 08:48 Best angle=0, nBlocks=1, nTracks=10, smallBlockScore=0, score=20.0
2021-12-26 08:48 Block 1 has 10 tracks
2021-12-26 08:48 Generated 10 tracks for this block
2021-12-26 08:48 generation 2 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 3 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 4 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 5 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 6 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 7 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 8 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 9 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 generation 10 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 1(4)- f = 165.3, d = 60.5 m
2021-12-26 08:48 Connecting track to block 1 has 12 points
2021-12-26 08:48 1. block 1, entry corner 4, direction to next = 1, on the bottom = false, on the left = true
2021-12-26 08:48 ####### COURSE GENERATOR END ###########################################################

Full Log https://pastebin.com/ag8usbHz

Resandise · 2021-12-26T14:59:49Z

Also, This was happens in versions 7.0.0.4 and 7.0.0.5

Tensuko · 2021-12-26T18:31:26Z

Sry buddy but I could not reproduce this, looks good to me in 7.0.0.5
Might be a old bug that needs a reset of the tool ?

log.txt

PeanutthaKid · 2021-12-26T20:07:25Z

I was able to do this in version 7.0.0.6 using a cultivator.

2021-12-26 14:03 Generating course, width 13.5 m, headlands 2
2021-12-26 14:03 ####### COURSE GENERATOR START ##########################################################
2021-12-26 14:03 Headland mode normal, number of passes 2, center mode up/down, min headland turn angle 60.0
2021-12-26 14:03 Width 13.5, headland first true, clockwise true. Skip rows 0
2021-12-26 14:03 Generating headland track with offset 6.75, clockwise true, inward true
2021-12-26 14:03 Generated headland track #1, area 3093, clockwise = true
2021-12-26 14:03 Generating headland track with offset 12.55, clockwise true, inward true
2021-12-26 14:03 Generated headland track #2, area 884, clockwise = true
2021-12-26 14:03 Added 54 (of 55) waypoints to headland 1 (add straight section), starting at 6
2021-12-26 14:03 Added 0 waypoints to reach a straight section for the headland 1 lane change after 5.3 m, r = 110437648340268.1
2021-12-26 14:03 Linked headland track 1 to next track, heading 33.5, distance 20.2, inwardAngle = 60
2021-12-26 14:03 Added 36 (of 91) waypoints to headland 2 (add full round), starting at 6
2021-12-26 14:03 Added 36 (of 127) waypoints to headland 2 (add straight section), starting at 42
2021-12-26 14:03 ROW ANGLE: FINDING THE OPTIMUM ANGLE
2021-12-26 14:03 Best angle=92, nBlocks=1, nTracks=1, smallBlockScore=0, score=11.1
2021-12-26 14:03 Block 1 has 1 tracks
2021-12-26 14:03 Generated 1 tracks for this block
2021-12-26 14:03 generation 2 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 3 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 4 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 5 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 6 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 7 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 8 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 9 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 generation 10 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 1(1)- f = 354.7, d = 28.2 m
2021-12-26 14:03 Connecting track to block 1 has 11 points
2021-12-26 14:03 1. block 1, entry corner 1, direction to next = 1, on the bottom = true, on the left = true
2021-12-26 14:03 ####### COURSE GENERATOR END ###########################################################

2021-12-26 14:14 Generating course, width 8.4 m, headlands 2
2021-12-26 14:14 ####### COURSE GENERATOR START ##########################################################
2021-12-26 14:14 Headland mode normal, number of passes 2, center mode up/down, min headland turn angle 60.0
2021-12-26 14:14 Width 8.4, headland first true, clockwise true. Skip rows 0
2021-12-26 14:14 Generating headland track with offset 4.20, clockwise true, inward true
2021-12-26 14:14 Generated headland track #1, area 3667, clockwise = true
2021-12-26 14:14 Generating headland track with offset 7.81, clockwise true, inward true
2021-12-26 14:14 Generated headland track #2, area 1993, clockwise = true
2021-12-26 14:14 Added 59 (of 60) waypoints to headland 1 (add straight section), starting at 8
2021-12-26 14:14 Added 0 waypoints to reach a straight section for the headland 1 lane change after 5.0 m, r = 198895137622974.6
2021-12-26 14:14 Linked headland track 1 to next track, heading 33.8, distance 12.6, inwardAngle = 60
2021-12-26 14:14 Added 46 (of 106) waypoints to headland 2 (add full round), starting at 7
2021-12-26 14:14 Added 46 (of 152) waypoints to headland 2 (add straight section), starting at 53
2021-12-26 14:14 ROW ANGLE: FINDING THE OPTIMUM ANGLE
2021-12-26 14:14 Best angle=0, nBlocks=1, nTracks=6, smallBlockScore=0, score=16.0
2021-12-26 14:14 Block 1 has 6 tracks
2021-12-26 14:14 Generated 6 tracks for this block
2021-12-26 14:14 generation 2 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 3 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 4 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 5 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 6 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 7 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 8 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 9 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 generation 10 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 1(4)- f = 398.3, d = 25.1 m
2021-12-26 14:14 Connecting track to block 1 has 5 points
2021-12-26 14:14 1. block 1, entry corner 4, direction to next = 1, on the bottom = false, on the left = true
2021-12-26 14:14 ####### COURSE GENERATOR END ###########################################################

During my testing, these tools were new purchases each time.

Also, was able to reproduce using Case IH 7150 Combine with 8.5m header and using NH T8 tractor with Amazone Citan 15001-C Seeder

Essentially the course generator is getting the correct working width, but the UI is showing an incorrect size.

cqusmc · 2021-12-26T22:03:11Z

When generating course for Krone Big X 1180 with X-Collect 900-3, when I set the Work Width in CP to the work width that the shop says for the X-Collect of 9 m, the course generates too big. (First 3 screenshots)

In your game's General Settings page, do you have your measuring unit set to 'Miles'? I had the same issue until I changed mine to the default 'Kilometers' and then reloaded the save. I think the Courseplay GUI is applying the 1 km -> 0.62 mi conversion factor, which is why it generates a larger course if you increase it from what was auto-detected.

PeanutthaKid · 2021-12-26T22:13:30Z

In your game's General Settings page, do you have your measuring unit set to 'Miles'? I had the same issue until I changed mine to the default 'Kilometers' and then reloaded the save. I think the Courseplay GUI is applying the 1 km -> 0.62 mi conversion factor, which is why it generates a larger course if you increase it from what was auto-detected.

Running the calculator, that's exactly what is happening. 8.4m (cultivator width) x 0.62 = 5.208 (close enough to the setting CP is showing in the Course Generator UI).

BullFlag · 2021-12-27T16:18:26Z

QUOTE In your game's General Settings page, do you have your measuring unit set to 'Miles'? I had the same issue until I changed mine to the default 'Kilometers' and then reloaded the save. How the issue was fixed for me too.( work-around for now ), Don't use "Miles" as measuring unit , choose km and save and reload

Resandise · 2021-12-29T05:41:36Z

Yes I have my settings set to Miles.

Tensuko · 2021-12-29T17:47:53Z

Can you try 7.0.0.9 and check if this is still a problem and also try miles and km ?
We would like to know if the problem persists and if so, is it a miles problem.

Resandise · 2021-12-29T19:33:48Z

Using 7.0.0.9, when setting is set to miles, the Work Width is still incorrect in the course generation menu, but when switched to KM and restarted the game, the Work Width is set right. When switched back to Miles, and restarted the game, it goes back to being incorrect. I appears to be only when the game is set to Miles that this issues exist. Not sure if there is any thing that can be done, as it might be inherent to the base game itself.

schwiti6190 · 2021-12-30T18:05:40Z

@Resandise Can you test this with the current main branch ?

Resandise · 2021-12-31T03:56:05Z

@schwiti6190 I downloaded the current version (7.0.0.10). When the settings is set to KM, to work width in the course generator menu is showing correct, but when set to Miles, it still shows incorrect. I did restart the game after each change of settings.

schwiti6190 · 2021-12-31T10:07:06Z

@Resandise My bad, I mean the current developer status and not the current release.

Only for this test, otherwise please stick to the releases :)

- Field scanner tuning (may help with #292) - Always use AI markers for plow offset - Turn fix for #283 - Wait for implements lower after turn ( #277, #288, #251 ) - Pathfinder turn fix #188 - Course generator fix for #263 - Could fix #128 - Disabled Shovel/shield auto workwidth #261 - Should fix #275 - Fix for percentage parameters - Course generator settings added - Combine pocket fix #284

PeanutthaKid · 2022-01-02T21:30:30Z

Problem persists in 7.0.0.11

2022-01-02 15:27 Generating course, clockwise 1, width 18.1 m, turn radius 5.3 m, headlands 0, startOnHeadland 1
2022-01-02 15:27 headland corner 1, headland overlap 7, center mode 1
2022-01-02 15:27 row direction 5, rows to skip 0, rows per land 6
2022-01-02 15:27 ####### COURSE GENERATOR START ##########################################################
2022-01-02 15:27 Headland mode none, number of passes 0, center mode up/down, min headland turn angle 150.0
2022-01-02 15:27 Width 18.1, headland first true, clockwise true. Skip rows 0
2022-01-02 15:27 Generating headland track with offset 0.00, clockwise true, inward true
2022-01-02 15:27 Added 75 (of 75) waypoints to headland 1 (add full round), starting at 2
2022-01-02 15:27 Added 75 (of 150) waypoints to headland 1 (add straight section), starting at 77
2022-01-02 15:27 ROW ANGLE: FINDING THE OPTIMUM ANGLE
2022-01-02 15:27 Best angle=90, nBlocks=1, nTracks=5, smallBlockScore=0, score=15.0
2022-01-02 15:27 Block 1 has 5 tracks
2022-01-02 15:27 Generated 5 tracks for this block
2022-01-02 15:27 generation 2 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 3 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 4 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 5 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 6 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 7 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 8 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 9 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 generation 10 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 1(2)- f = 826.8, d = 12.1 m
2022-01-02 15:27 Connecting track to block 1 has 70 points
2022-01-02 15:27 1. block 1, entry corner 2, direction to next = -1, on the bottom = true, on the left = false
2022-01-02 15:27 ####### COURSE GENERATOR END ###########################################################

Resandise · 2022-01-03T04:20:32Z

Using 7.0.0.11, this issue still exist.

VergylTantor · 2022-01-04T19:18:31Z

I agree that this is still an issue with 7.0.0.12. Should this Issue be reopened?

schwiti6190 · 2022-01-05T20:16:40Z

Could somebody explain to me what would be an appropriate alternative to meters, other than miles ?

VergylTantor · 2022-01-05T20:40:26Z

Unfortunately, I can't think of an alternative to miles in the Imperial measurement for length because that is what is used on vehicle speedometers.

…

On Wed, Jan 5, 2022 at 2:16 PM schwiti6190 ***@***.***> wrote: Could somebody explain to me what would be an appropriate alternative to meters, other than miles ? — Reply to this email directly, view it on GitHub <#128 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJM6R54OCMGP6XR6X5DFXUTUUSRLJANCNFSM5KY7UB6Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

schwiti6190 · 2022-01-06T06:23:56Z

Either these settings stay in meter values or we could use something different, as 0.1m = 0,000621371 miles would be a pain to display and work with :)

PeanutthaKid · 2022-01-06T07:07:44Z

feet would be the alternative to meters. 1 meter is equal to 3.28 feet

VergylTantor · 2022-01-06T14:48:54Z

I can't speak for anyone else, but I would have no problem with decoupling the FS22 "Measuring Distance" setting from Courseplay. I am used to having meters displayed by Courseplay and using it to adjust path width, like it was in v5.00 and v6.xx.

Resandise · 2022-01-06T14:57:58Z

Yards would be the closes imperial measurement to meters. 1 yd = 0.9144 meters or 1 meter = 1.09 yds. Also, 1 yd = 3 feet.

We removed the H key binding to start Courseplay, H will now start the built-in helper (or bring up the helper screen) as in the vanilla game. To start the Courseplay helper, there is a new Action (CP Start driver) you can now assign to any key combination in the Keyboard Controls screen, we recommend using Ctrl+H. - Better corners when scanning fields #337 - End of course offset fixed (again) #323 - Pathfinder debug overlap box disabled - Work width calculation fix #354 - Moved course display to the background behind the course generator settings fixes #343 - Disabled activating Cp with default keybinding #190 - Added start cp keybinding #190 - Minor fix/refactor for course generator, fixes #352 - Reversing tuning, might help with #378 and closes #353 - Should fix #348 for now - Added imperial unit foot #128 - fixes #374 - No pathfinder for simple wide turns #340

Tensuko · 2022-01-06T16:08:55Z

Pls try 7.0.0.13
Reopen if Issue persists.

VergylTantor · 2022-01-06T16:59:52Z

The screenshot is taken with a 15-meter implement, which would be 49.2126 feet. I don't know if you are multiplying or dividing but the conversion numbers would be .3048 or 3.28.

Resandise · 2022-01-07T04:03:08Z

Re-Opened, issue #400

PeanutthaKid · 2022-01-07T18:19:56Z

Still no fix on .16

BullFlag · 2022-01-07T20:00:53Z

I'm fine just staying with km only. I think the whole FS code base is in meters, both map and vehicles. LIkely there's other priorities more important than "miles". I'm fine with removing "km/miles" option for a few months. This seems so minor compared to dealing with an entirely new interface in the Giant's Workers menu ( which might be impossible to change to fit CP needs )

- Another fix for cotton harvester #421 - Allow reverse pathfinding option re-enabled #102 - Field scanner improvement #417 - Set start job on first waypoint as default - Set default keybinds for open mini hud and start/stop CP Driver - Keybind for CP now also stops CP - Disable last waypoint callback for combine headland turn (fix for Claas Dominator) - Leftover reversing debugs removed #394 - Another imperial unit fix for #128 - Don't show pathfinder debug boxes #426 - Stop chopper only if it is harvesting #411 - Smal turn fix - Headland to up/down transition fix #340

Resandise mentioned this issue Dec 26, 2021

Plow work width #19

Closed

Tensuko assigned pvaiko Dec 26, 2021

Tensuko added the can't reproduce reproduction impossible label Dec 26, 2021

Tensuko changed the title ~~Work Width not correct.~~ Work Width not correct. km/miles problem ? Dec 27, 2021

Tensuko removed the can't reproduce reproduction impossible label Dec 27, 2021

schwiti6190 closed this as completed in 59b602c Dec 30, 2021

Tensuko mentioned this issue Jan 1, 2022

Implement width[BUG_SP] #288

Closed

pvaiko assigned schwiti6190 and unassigned pvaiko Jan 3, 2022

schwiti6190 added a commit that referenced this issue Jan 6, 2022

Added imperial unit foot #128

439c14d

Tensuko mentioned this issue Jan 6, 2022

Working Width display (number) is wrong #376

Closed

schwiti6190 added a commit that referenced this issue Jan 6, 2022

Another imperial unit fix for #128

e3f9364

This was referenced Jan 7, 2022

Incorrect unit conversion [BUG_SP] #398

Closed

Imperial Units not being correctly converted in Course Generator [BUG_SP] #409

Closed

This was referenced Jan 8, 2022

[BUG_SP] Incorrect width in GUI #422

Closed

Tool width #432

Closed

[Feature] Add a "reset working width" button when generating courses #198

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Work Width not correct. km/miles problem ? #128

Work Width not correct. km/miles problem ? #128

Resandise commented Dec 26, 2021

Resandise commented Dec 26, 2021 •

edited

Loading

Tensuko commented Dec 26, 2021

PeanutthaKid commented Dec 26, 2021 •

edited

Loading

cqusmc commented Dec 26, 2021

PeanutthaKid commented Dec 26, 2021 •

edited

Loading

BullFlag commented Dec 27, 2021

Resandise commented Dec 29, 2021

Tensuko commented Dec 29, 2021

Resandise commented Dec 29, 2021

schwiti6190 commented Dec 30, 2021

Resandise commented Dec 31, 2021 •

edited

Loading

schwiti6190 commented Dec 31, 2021

PeanutthaKid commented Jan 2, 2022

Resandise commented Jan 3, 2022

VergylTantor commented Jan 4, 2022 •

edited

Loading

schwiti6190 commented Jan 5, 2022

VergylTantor commented Jan 5, 2022 via email

schwiti6190 commented Jan 6, 2022

PeanutthaKid commented Jan 6, 2022

VergylTantor commented Jan 6, 2022 via email

Resandise commented Jan 6, 2022 •

edited

Loading

Tensuko commented Jan 6, 2022

VergylTantor commented Jan 6, 2022 •

edited

Loading

Resandise commented Jan 7, 2022

PeanutthaKid commented Jan 7, 2022

BullFlag commented Jan 7, 2022 •

edited

Loading

Work Width not correct. km/miles problem ? #128

Work Width not correct. km/miles problem ? #128

Comments

Resandise commented Dec 26, 2021

Resandise commented Dec 26, 2021 • edited Loading

Tensuko commented Dec 26, 2021

PeanutthaKid commented Dec 26, 2021 • edited Loading

cqusmc commented Dec 26, 2021

PeanutthaKid commented Dec 26, 2021 • edited Loading

BullFlag commented Dec 27, 2021

Resandise commented Dec 29, 2021

Tensuko commented Dec 29, 2021

Resandise commented Dec 29, 2021

schwiti6190 commented Dec 30, 2021

Resandise commented Dec 31, 2021 • edited Loading

schwiti6190 commented Dec 31, 2021

PeanutthaKid commented Jan 2, 2022

Resandise commented Jan 3, 2022

VergylTantor commented Jan 4, 2022 • edited Loading

schwiti6190 commented Jan 5, 2022

VergylTantor commented Jan 5, 2022 via email

schwiti6190 commented Jan 6, 2022

PeanutthaKid commented Jan 6, 2022

VergylTantor commented Jan 6, 2022 via email

Resandise commented Jan 6, 2022 • edited Loading

Tensuko commented Jan 6, 2022

VergylTantor commented Jan 6, 2022 • edited Loading

Resandise commented Jan 7, 2022

PeanutthaKid commented Jan 7, 2022

BullFlag commented Jan 7, 2022 • edited Loading

Resandise commented Dec 26, 2021 •

edited

Loading

PeanutthaKid commented Dec 26, 2021 •

edited

Loading

PeanutthaKid commented Dec 26, 2021 •

edited

Loading

Resandise commented Dec 31, 2021 •

edited

Loading

VergylTantor commented Jan 4, 2022 •

edited

Loading

Resandise commented Jan 6, 2022 •

edited

Loading

VergylTantor commented Jan 6, 2022 •

edited

Loading

BullFlag commented Jan 7, 2022 •

edited

Loading