LeroyJenkins420
-
Posts
201 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by LeroyJenkins420
-
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
How much Ram does your server have? Is it possible it was lagging during this time? I could easily see lag potentially causing these issues -
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
When those pieces "Fall off" the train so to speak the collider is still on the train so it will not make the train get stuck. What you showed in the screenshot though is a separate bug from that. Are you experiencing both? Invisible blocks in place, and also blocks "falling off" visually? I'm on Oxide server now, running the latest version of the plugin (AND ONLY MY PLUGIN) and I cannot recreate the bugs you are describing. What I am doing I spawned a train Workcart_Aboveground I built walls and roof on the train I put fuel in it I go forward I travel multiple grids without issue I leave the train and go somewhere else on the map (roughly for 5 minutes) I go back to the train and drive it again for some distance without issue What you have described to me is not occurring locally on my end which leads me to believe some other plugin is causing a conflict. If you would like to paste a list of the plugins you are using I would be happy to take a look, or you're also welcome to DM them to me. -
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
Hello @SkeletonKing69, Thank you for the information, I still would like to know a time frame particularly of the blocks lifespan, EX "I placed the block on the train ran away for like 5 minutes, came back within distance of the train for 2 minutes, then it went invisible" I dont believe LODS are the issue here, there is likely some underlying issue with the network update. Your client isnt getting those block updates even though I send them to everyone within the trains network group, if there are players nearby. Before releasing this latest update I had tested both on Oxide and Carbon to ensure no blocks get left behind or go invisible. My tests for both server types included building a small train, then letting it drive around the rail network while I watched. During this time I did not observe any blocks being left behind, the test ran for roughly 2 hours before I concluded the build stable. I'm starting my Oxide server now so we'll see if that still holds true. -
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
Thank you, I just tested on Carbon with the same Workcart_AboveGround train type and I couldnt seem to produce the same result. Im going to try on Oxide next. Can you tell me more information about what you were doing before this happened? Mainly im concerned with knowing when was the train spawned was it one you spawned or a "wild" one? Did this happen immediately after building on it, what time frame? Was it after moving or before or both? Do you notice it with specifically the type mentioned or with all types? -
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
-
Train Pieces still left behind
LeroyJenkins420 replied to SkeletonKing69's Support Request in Support
Hello @SkeletonKing69 are you on oxide or carbon? -
Hello @Klyowa did you delete the config files from the previous update? If you are performing a fresh install of the plugin there should be no issues. If you continue to have issue though feel free to also reach out to me on discord @Schmenkins Also moving forward if you have issue, could you open a support request to make it easier to track and not clog up discussions? -
Hello @Klyowa apologies for the delay, the latest update fixes this! Enjoy -Leroy
-
Changed Status from Pending to Fixed Changed Fixed In to 1.0.2
-
Just released the latest update which fixes this Enjoy! -Leroy
-
Hey @xlr8tednergy I have an update that fixes this ready, i'm finalizing oxide compatibility now and should be able to post it.
-
Providing an update here, I have tested the update quite extensively and it seems solid. This should be released sometime tomorrow once I verify Oxide compatibility.
-
Hello @Klyowa, I've a version that has fixed this bug, i'll be posting it soon. I found that the monobehavior that sends my updates wasnt getting added back to the game object on plugin reload. I apologize in advance for any inconvenience -Leroy
-
No errors necessarily, Just some interesting activity
LeroyJenkins420 replied to xlr8tednergy's Support Request in Support
that preset was not supposed to be in this patch you're welcome to keep it in, but i'd recommend removing it from the config -
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.0.1
-
Hey @urmarel, I couldnt agree with you more, and thank you for including your troubleshooting! Also I laughed way to hard at the last bit of your reply. Im not sure what your issue may have been, however if you encounter it again do creative.freeplacement true in your f1 console. This should fix the building to close to road error Glad to hear you enjoy the plugin and would love to see a review from you if you dont mind
-
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.0.1
-
Hey @Butters this is fixed now!
-
Getting this error after forcewipe
LeroyJenkins420 replied to xlr8tednergy's Support Request in Support
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.0.1 -
Changed Status from Pending to Fixed Changed Fixed In to 1.0.1
-
Changed Status from Pending to Work in Progress
-
Hi @urmarel please reach out to me on discord @Schmenkins and i'll be happy to look into this further.
-
Changed Status from Pending to No Response
-
Hey @xlr8tednergy the "shittles" is a logging statement I use sometimes. Its in your config, you can delete the whole line, secondly im pretty sure this plugin is broken atm, multiple customers are reporting a "Not Enough Space" error, I believe Facepunch has changed something. For the time being I would unload the plugin until I can release a patch
-
you can also spawn them yourself with "spawn wagonc" or other train short name in your rust console.