Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback for Development Release 4 #26

Open
wildex999 opened this issue Feb 6, 2016 · 23 comments
Open

Feedback for Development Release 4 #26

wildex999 opened this issue Feb 6, 2016 · 23 comments

Comments

@wildex999
Copy link
Owner

I have just released Development version 4, and I'm getting close to the final 0.2.0 release, before I start working on the next feature set.

I would appreciate it if you could take the time to test a release for your server(Taking world backup first!!!) and giving some feedback on what works and what doesn't while running on a loaded server.

I have released dev4 for KCauldron, Forge 1.7.10 and Forge 1.8.9. You can find them under releases here: https://github.com/wildex999/TickDynamic/releases

Changes for dev4

  • Implemented a missing method which could have causes problems. (Fixes player respawn in KCauldron)
  • Handle case where removing a Entity/Tile which is the last one iterating, causes it to fail. (Should stop desync message for players in KCauldron)
  • Better debugging messages.

Changes for dev3

  • Worlds should now properly unload without leaking
  • Added new command: 'reloadgroups', which will reload all groups, and reassign any loaded Entities or TileEntities into the new group setup. Note: This is currently a brute force approach, I would appreciate any feedback on the impact this command has on a server under load.
  • Config fixes, it should now more properly respect global groups and default settings.
  • Entities should now properly unload
  • Other stability fixes

Known Problems

  • None yet

Reporting problem

  • If you have a problem you can reproduce, please set 'debug = true' in the config and upload a log when reporting the problem.
@spannerman79
Copy link

I'll test the Forge 1.7.10 build soon(ish). Long story short I had to stop using kcauldron and move to a vanilla forge instance. It wasn't by choice (many of my users have some sort of development issue being Autistic, ADHD, etc).

@wildex999
Copy link
Owner Author

@spannerman79 Yeah, so far KCauldron has been more problem than it's worth, so I don't think I'll support it past 0.2. For 1.8 Sponge seems to be the thing =)

@spannerman79
Copy link

For 1.8 Sponge seems to be the thing =)

Sure is 👍 Not there yet with the number of mods or their function to move fully over to SpongeForge ..yet

@filthy1337
Copy link

I have tested TickDynamic Dev v3 on my Feed the Beast Infinity Evolved server (2.3.5) with KCauldron-1.7.10-1614.193. There is no crash, but the server just kinda stops before it gets fully up on-line. :/
Is there anything I could try to do to make this mod work for me?

@spannerman79
Copy link

@filthy1337 Logs? Use gist or upload the uncompressed log here

@badgernz
Copy link

I have run it on a loaded Infinity server aswell but with KCauldron:1.7.10-1614.174 and have had no loading errors, just crashes when you try use tick profiler and/or opis

http://pastebin.com/AKXCs91M

@spannerman79
Copy link

just crashes when you try use tick profiler and/or opis

@badgernz Use mapless Opis from here or here

@wildex999
Copy link
Owner Author

@filthy1337 Could you upload your logs somehwere(pastebin, gist etc.) and post it here? "kinda stops" doesn't help me much unfortunately =(

@badgernz Yeah, compatibility with other mods which heavily modifies/depends on the world loop(Like Opis and Tick Profiler) will work poorly with TickDynamic.
I might make it compatible on Forge servers at some point, but KCauldron is just too much of a minefield to even try.

Thank you both for taking the time to test and report here =)

@filthy1337
Copy link

Hey! I reinstalled my server (FTB Infinity Evolved 2.3.5) from scratch and and now TickDynamic Dev v3 works as it should. I guess the problem was not in TickDynamic itself (although the problem appeared only after adding TickDynamic and went away by disabling it?), but some other thing that I just couldn't figure out... :/ Well, anyway thanks for this great mod!! Keep up the good work!!

@wildex999
Copy link
Owner Author

@filthy1337 Reinstalled as in started a new world?
There might be certain things that doesn't cause problems unless they exist in the world etc.
If it suddenly starts happening again, it would be nice to know what caused it =)

@filthy1337
Copy link

I actually installed the whole server again from the ground up. :) Downloaded the FTB pack, KCauldron and TickDynamic just so that there was no possibility of unrelated errors confusing me even more! :D If it stops working again I now have a better chance to find out what could have caused the problem in the first place. I'll keep you posted...

@spannerman79
Copy link

Ok so I want to test out the forge 1.7.10 version of the dev release ( https://github.com/wildex999/TickDynamic/releases/tag/Forge1.7.10_0.2.0-dev3 ), but to really test it out i want to be able to add some groups in.

Does anyone have any groups in their config file setup that they are willing to share?

@spannerman79
Copy link

@wildex99 do you have some recommended group settings in order for me to test out your groups option on my forge 1.7.10 server?

@wildex999
Copy link
Owner Author

@spannerman79 Not really. I originally added the group system to allow for excluding mods which was not compatible with Dynamic Ticking.
When I test I mostly just throw Entities like Pigmen into their own groups just to see that it works.

I would recommend you just start putting things you think use a lot of time(Enemy mobs for example) into their own group, and then check how much time they actually use to further plan out the groups.
The group reload should work now, so you can do rapid testing.

As I might have mentioned earlier, I don't yet have a full server to actually test the mod on, which is why I created this thread =)

@wildex999 wildex999 changed the title Feedback for Development Release 3 Feedback for Development Release 4 Feb 19, 2016
@wildex999
Copy link
Owner Author

I have now released Development version 4. Feedback continues in this ticket for now.

This update is mostly targeted at KCauldron users, but the problems might appear in other servers also, so upgrade if you have any problems.

@filthy1337
Copy link

Tested this dev build 4 and got a crash. crash-2016-02-20_14.59.27-server.txt

@wildex999
Copy link
Owner Author

@filthy1337
Copy link

I will definitely test it! Thanks! :)

@filthy1337
Copy link

For twice now I have had a client crash which has never happened before... Is it a coincidence or TickDynamic related?
crash-2016-02-21_01.40.05-client.txt
crash-2016-02-21_12.27.57-client.txt

@spannerman79
Copy link

@filthy1337 open an issue over at the correct issue tracker - http://minecraft.curseforge.com/projects/decocraft2/issues

@wildex999
Copy link
Owner Author

Unless you are running TickDynamic on the client, I can't see how it can cause this. Won't rule it out entirely though. TickDynamic has nothing to do with the chunks being sent to the client, and this seems to be entirely a client error.

The crashing mod needs to throw in a "instanceof" check before casting it seems to me ;)

@filthy1337
Copy link

Okay, I got a new error now:
crash-2016-02-26_23.19.59-server.txt

@enterprise12nx
Copy link

I moved to thermos from Kcauldron when it started running smoother, and then i saw Kcauldron dissapeared, i remember @spannerman79
Hoping some support can come to Thermos, but i can understand working towards sponge (hurry up!)
@wildex999

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants