Cuberite Forum
Random Chitchat 2012-2016 - Printable Version

+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Off Topic (https://forum.cuberite.org/forum-9.html)
+--- Forum: Off Topic Discussion (https://forum.cuberite.org/forum-10.html)
+--- Thread: Random Chitchat 2012-2016 (/thread-434.html)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487


RE: What we're doing - tonibm19 - 12-12-2013

(12-12-2013, 10:28 AM)tigerw Wrote: How does MCS compare?

In my server MCS is lag free, and uses less ram. The great thing of bukkit is that it has all features and a good chunk manager. Ram has 151 mb free. The server has been up 1 day and me and one friend played on it. Also, it's very stable.


RE: What we're doing - NiLSPACE - 12-13-2013

Just found something pretty usefull. Using F3 + B you can see the hitbox of an entity: [Image: 5KlWS.jpg] [Image: 5KlZJ.jpg]


RE: What we're doing - ThuGie - 12-13-2013

Quite a bit hitbox for the xp orb.


RE: What we're doing - xoft - 12-13-2013

Weird thing has started happening to me. I set up a breakpoint in Decoda, that is hit everytime a player spawns in a world (HOOK_PLAYER_SPAWNED), and when the breakpoint is hit, Decoda pauses MCS, but it still manages to mis-parse the protocol, producing weird packet errors. I have no idea what's going on here, I'm suspecting a threading issue which could manifest in normal gameplay, but it hasn't yet, and the breakpoint amplifies it. But still, it's plain weird.

Yup, threading issue, a complicated one. Finally I untangled the mess.
1. The player connects
2. The client handle is created and added to cServer; the cServer's TickThread handles the packet processing for the client
3. The player logs in and spawns, the packet handler moves the client handle from the cServer to the specified cWorld and calls the OnPlayerSpawned hook.
4. Decoda breakpoint causes the cServer's TickThread to pause.
5. cWorld's TickThread is now in charge of handling the packets for the client handle; the thread is not paused by Decoda, so it runs and receives next packet
6. The next packet is stored in the ByteBuffer after the initial login packet
7. The next packet is processed and the ByteBuffer resets to the beginning of the "currently parsed" packet, to skip the PacketSize bytes of the packet correctly. However, because the login packet hasn't still been committed as processed, the ByteBuffer resets in front of the login packet instead of the next packet.
8. Bam, protocol error!

The question now is, how to handle this mess. And it doesn't need to be caused just by Decoda, it could be anything in a plugin taking a bit longer in the OnPlayerSpawned hook.


RE: What we're doing - xoft - 12-14-2013

Just bought Fallout *for free* on http://gog.com . Maybe this time I'll actually enjoy the game.

Threading issue fixed. Along with possibly a few others. Now packets are read full, separated into a new cByteBuffer, and only then processed.


RE: What we're doing - NiLSPACE - 12-14-2013

Does that also fix #187?


RE: What we're doing - xoft - 12-14-2013

No, unfortunately not. That's a completely different issue, although it keeps bugging me quite a lot, too.


RE: What we're doing - tonibm19 - 12-14-2013

Yesterday I got my new computerTongue.
Intel core i5
nVidia gForce GTX 650 2g ddr5
8GB RAM DDR5

Do you think it will run Battlefield 4 well? Smile


RE: What we're doing - xoft - 12-15-2013

I've been spending some time trying to compile Qt from source, because they no longer distribute the MSVC2008 binary package. It's been 5 days already and still it doesn't work Sad


RE: What we're doing - tigerw - 12-15-2013

It doesn't work because VS2008 isn't supported anymore, or something else?

(12-14-2013, 06:31 AM)tonibm19 Wrote: Yesterday I got my new computerTongue.
Intel core i5
nVidia gForce GTX 650 2g ddr5
8GB RAM DDR5

Do you think it will run Battlefield 4 well? Smile

I'm sure it will, the specifications seem fast.