console only outputting /dhs
Anyone know what's going on here? I'm on the DHS-0.9.0-SNAPSHOT_for_MC-1.21.4 nightly build for DH plugin and this is what the console looks like. I've folllowed the wiki too to the best of my knowledge.
Solution:Jump to solution
I think i have made a deadlock condition when the number of scheduler threads is too low
69 Replies
Update to the latest nightly. Command format and feedback has changed earlier this week.
ah alright, i see the outputs now
and the output of infinity time is expected too?
Lol
That's not something I added
The value might be overflowing the data type I'm using
oh LOL alright 🤔 interesting though that the server doesn't seem to be doing anything
Well, then at least the estimate is correct
in the case that the server is just on idle, is that expected then? 😂
Have you changed anything in the plugin config file?
I did, but I didn't think it would affect it in this way, here:
im specifically trying to pregen the nether right now btw
Ah
Solution
I think i have made a deadlock condition when the number of scheduler threads is too low
Try increasing it
oh 😮 okay will try it out
ill put it back to the default and see what happens
beautiful, that did the trick 👌
Alright nice
thanks a ton!
I'm out right now, but will attempt a fix from the phone. Should be an easy one
sounds good 🙂
This should fix it. Feel free to test that build when it completes
With 1 thread that is
sounds good 🙂 ill take a look tomorrow if that's okay!
I'll put this comment in the same thread since it's somewhat related
this is the output so far for the command /dhs pregen start Spawn_nether -53 -202 512
The coordinate -53 -202 is found inside the L shape render. Interestingly, there's a huge block up there with a radius of approx -3617 - (-8977) = 5360, centered at approx -3617, -12853
I find where's it's centered a bit strange 🤔 any ideas here?
For better guestimates on the coordinates of the square it's
x is between -8928 to 2207
z is between -18465 to -7265
Hm. I have probably only been testing with a center of 0x0, so any weirdness in the math would have been hidden
Let's see
yeah i wonder if it being the nether too further messes things up, thanks for looking into it so quick 🙂
We pass the coordinates from the pregen command directly through to the pregen class, which deals with section positions, not block positions. This means the coordinates are scaled incorrectly by a factor of 64
Ah, so it is a bug?
Very much so :)
Gotcha xD
I am working on a different feature rn, but I'll fix that real quick
Sounds good! Thanks!
Try this one when it completes
Okok will do!
It also adds the config option to disable chunk generation, so you'll only get LODs for pre-existing areas
Alright!
Out of curiosity, can I technically delete the pregen'd lods I loaded up as above running some sql command/query? I'm guessing it's not as easy as that LOl no clue what the structure of the db looks like xD
I only bring it up because nobody will probs be going to those lods I pregenerated LOL it's okay if there's nothing I can do though!
You absolutely can :) There are tools to browse and manipulate SQLite files
The data looks like this
Coordinates are section positions, which is just block coordinates divided by 64
Someone asked for a "trim" command before, and I guess this would be a use-case for that as well
Yeah I use db browser on my own stuff haha. I can probably make a query someone can run if I think about it 🤔 I'll touch it later then
If you're asking for a specific query, I guess it would be something like this:
That would delete anything outside of a 1024 chunk distance from 0x0
You would probably define other ranges that fit your server
Ah I guess that's a simpler query yeah, I was thinking more of a query that has 4 numbers that define the coordinates of a rectangle, but yeah this works too for my case 🙂
If your center is somewhere at least close to 0x0, sure
Indeed
hmm, is there a way to determine what world is attached to the worldId? i want to be seletive of what world im touching before i delete
Good question
im thinking timestamp is probs just the best guestimate 🤷♂️
Or count the number of LODs per world
I'm guessing your nether will have the most
oh, the overworld definitely has a lot right now LOL
lol
trying this out, but i think the db is too big at this point select * from lods order by timestamp DESC limit 100;
I can slap together a command that shows all worlds and their IDs pretty quickly, if that helps
oh, i've got that already, there's 3 worldIds i have
but idk which is which, i think ill try again and just find the latest change 🤔
latest record*
That's what I mean; show the names and IDs together
oh, that'd be amazing 😮
alright, i have a hunch of what i should set the worldId as, but ill wait for your sql command just in case
Ah sorry, I was thinking plugin command
oh LOL yeah that helps in the long run too 🙂
alright, ill try out a delete, hopefully it wont crash midway 😄
🤞
running
DELETE FROM lods WHERE worldId='8ffc2ad2-e6de-405a-b660-f495fb11722f' AND ( abs(x) > 1024 / 4 OR abs(z) > 1024 / 4)
oh, looks like it did something
Execution finished without errors.
Result: query executed successfully. Took 671ms, 5536 rows affected
At line 1:
DELETE FROM lods WHERE worldId='8ffc2ad2-e6de-405a-b660-f495fb11722f' AND ( abs(x) > 1024 / 4 OR abs(z) > 1024 / 4);
potentially good i guessNice
I'm gonna head to bed. Past 5 am here 🙈 Maybe I'll make that trim command tomrrow
yeah i guess this is about correct
sounds good 🙂 thanks again!
Likewise :) That center coordinate bug was a nice find
Let's hope I actually fixed it, and not just made it different
HAHAH yup that's how it always is 🤣
it looks like it's already doing a good job doing the correct LODs will check a bit later and tomorrow to see if this is indeed the case
also, /dhs worlds works and the worldId I suspected is the correct one too 🥳
as for the 2 scheduler thread stuff, ill check this after the LODs finish
here's the results
top most z cooridnate: -8417
second top most z coordinate: -7392
bottom most z coordinate: 8031
left most x cooridnate: -8225
right most x coordinate: 8223
also, it's for sure done the pregen
If it has completed, then "/dhs pregen status" will tell you there are no tasks running. If you've restarted the server while pregen was running, it will not have started back up automatically. You can run pregen again, and it will not regenerate LODs that already exist; only ones that are missing.
i've been running it all night, so it should've completed normally 🤷♂️ and yes i checked the status for this world and it seemed like it was done when i took this picture. I can try again later 😛
Could also be more issues with my math ofc 😅
yup could be xD but I think it's at least functionable for now