Hey I managed to recreate the physics items falling and bouncing through the floor bug if you're interested.
On 3/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > And another... > > > vphysics.dll!260a1f40() > vphysics.dll!260b6240() > vphysics.dll!2609444b() > vphysics.dll!260e577c() > vphysics.dll!260a2400() > vphysics.dll!260d3eae() > vphysics.dll!2608af8e() > vphysics.dll!2608b01b() > vphysics.dll!260a2697() > vphysics.dll!260aac2b() > vphysics.dll!2609cd5b() > vphysics.dll!2609cae9() > vphysics.dll!260967d8() > vphysics.dll!2601d878() > server.dll!22717c67() > server.dll!2269d1b4() > server.dll!22435ba8() > server.dll!22715283() > server.dll!227321f3() > server.dll!2269cd99() > server.dll!2269ccf8() > ws2_32.dll!71ab2b32() > ws2_32.dll!71abb230() > server.dll!22673f44() > server.dll!226740a2() > kernel32.dll!7c80a42b() > tier0.dll!00873e45() > engine.dll!0da9e42f() > engine.dll!0daa0691() > engine.dll!0da9b0e7() > engine.dll!0da9cc75() > engine.dll!0da03cd7() > engine.dll!0da04376() > engine.dll!0da0f025() > engine.dll!0da0f112() > user32.dll!77d496b8() > engine.dll!0da0f1af() > engine.dll!0daacefc() > engine.dll!0daac4ed() > dedicated.dll!1000c084() > engine.dll!0daacd4e() > engine.dll!0daac48b() > dedicated.dll!1000c535() > dedicated.dll!1000c553() > materialsystem.dll!00cd0dae() > materialsystem.dll!00cd0f38() > materialsystem.dll!00cd0dae() > materialsystem.dll!00cd0f05() > materialsystem.dll!00cd7f64() > materialsystem.dll!00cd9502() > tier0.dll!0087299f() > materialsystem.dll!00cda349() > tier0.dll!008764b5() > tier0.dll!0087105a() > tier0.dll!008731d0() > tier0.dll!008738de() > datacache.dll!00e7daa2() > datacache.dll!00e7e08e() > datacache.dll!00e733ae() > datacache.dll!00e73e6b() > engine.dll!0db556b8() > engine.dll!0db552dc() > engine.dll!0d9adc0d() > dedicated.dll!10021d0b() > dedicated.dll!10022c00() > dedicated.dll!10022c00() > dedicated.dll!1000c7f7() > ntdll.dll!7c9106eb() > > > At 2006/03/24 10:11 PM, Physical Mayhem Bug wrote: > >Here's a new one - slightly different, note the 260d0590... > > > > vphysics.dll!260a2426() > > vphysics.dll!260d3eae() > > vphysics.dll!260d0590() > > vphysics.dll!2608af8e() > > vphysics.dll!2608b01b() > > vphysics.dll!260a2697() > > vphysics.dll!260c6716() > > vphysics.dll!260aabf2() > > vphysics.dll!260aac2b() > > vphysics.dll!2609cd5b() > > vphysics.dll!2609cae9() > > vphysics.dll!260967d8() > > vphysics.dll!2601d878() > >> server.dll!PhysFrame(float deltaTime=0.015000000) Line 1341 C++ > > server.dll!CPhysicsHook::FrameUpdatePostEntityThink() Line 441 + > > 0x9 C++ > > server.dll!InvokeMethod(void (void)* f=0x223f4be2) Line 244 C++ > > server.dll!IGameSystem::FrameUpdatePostEntityThinkAllSystems() Line > > 221 + 0xa C++ > > server.dll!CServerGameDLL::GameFrame(bool simulating=true) Line 912 > > C++ > > engine.dll!0daa0691() > > engine.dll!0da9b0e7() > > engine.dll!0da9cc75() > > engine.dll!0da03cd7() > > engine.dll!0da04376() > > engine.dll!0da0f025() > > engine.dll!0da0f112() > > user32.dll!77d496b8() > > engine.dll!0da0f1af() > > engine.dll!0daacefc() > > engine.dll!0daac4ed() > > dedicated.dll!1000c084() > > engine.dll!0daacd4e() > > engine.dll!0daac48b() > > dedicated.dll!1000c535() > > dedicated.dll!1000c553() > > materialsystem.dll!00cd0dae() > > materialsystem.dll!00cd0f38() > > materialsystem.dll!00cd0dae() > > materialsystem.dll!00cd0f05() > > materialsystem.dll!00cd7f64() > > materialsystem.dll!00cd9502() > > tier0.dll!0087299f() > > materialsystem.dll!00cda349() > > tier0.dll!008764b5() > > tier0.dll!0087105a() > > tier0.dll!008731d0() > > tier0.dll!008738de() > > datacache.dll!00e7daa2() > > datacache.dll!00e7e08e() > > datacache.dll!00e733ae() > > datacache.dll!00e73e6b() > > engine.dll!0db556b8() > > engine.dll!0db552dc() > > engine.dll!0d9adc0d() > > dedicated.dll!10021d0b() > > dedicated.dll!10022c00() > > dedicated.dll!10022c00() > > dedicated.dll!1000c7f7() > > ntdll.dll!7c9106eb() > > > > > >At 2006/03/16 08:13 PM, [EMAIL PROTECTED] wrote: > >>Hmm this one's seemingly identical to the last one. > >> > >>> vphysics.dll!260a2426() > >> vphysics.dll!260d3eae() > >> vphysics.dll!2608af8e() > >> vphysics.dll!2608b01b() > >> vphysics.dll!260a2697() > >> vphysics.dll!260aac2b() > >> vphysics.dll!2609cd5b() > >> server.dll!221a22cc() > >> vphysics.dll!2609cae9() > >> vphysics.dll!260967d8() > >> vphysics.dll!2601d878() > >> server.dll!22196475() > >> server.dll!22194661() > >> server.dll!221946c0() > >> server.dll!22156317() > >> server.dll!22156292() > >> server.dll!2213d340() > >> engine.dll!0da9e42f() > >> engine.dll!0daa0691() > >> engine.dll!0da9b0e7() > >> engine.dll!0da9cc75() > >> engine.dll!0da03cd7() > >> engine.dll!0da04376() > >> engine.dll!0da0f025() > >> engine.dll!0da0f112() > >> user32.dll!77d496b8() > >> engine.dll!0da0f1af() > >> engine.dll!0daacefc() > >> engine.dll!0daac4ed() > >> dedicated.dll!1000c084() > >> engine.dll!0daacd4e() > >> engine.dll!0daac48b() > >> dedicated.dll!1000c535() > >> dedicated.dll!1000c553() > >> materialsystem.dll!00cd0dae() > >> materialsystem.dll!00cd0f38() > >> materialsystem.dll!00cd0dae() > >> materialsystem.dll!00cd0f05() > >> materialsystem.dll!00cd7f64() > >> materialsystem.dll!00cd9502() > >> tier0.dll!0087299f() > >> materialsystem.dll!00cda349() > >> tier0.dll!008764b5() > >> tier0.dll!0087105a() > >> tier0.dll!008731d0() > >> tier0.dll!008738de() > >> datacache.dll!00e7daa2() > >> datacache.dll!00e7e08e() > >> datacache.dll!00e733ae() > >> datacache.dll!00e73e6b() > >> engine.dll!0db556b8() > >> engine.dll!0db552dc() > >> engine.dll!0d9adc0d() > >> dedicated.dll!10021d0b() > >> dedicated.dll!10022c00() > >> dedicated.dll!10022c00() > >> dedicated.dll!1000c7f7() > >> ntdll.dll!7c9106eb() > >> > >> > >>At 2006/03/12 02:49 PM, [EMAIL PROTECTED] wrote: > >>>Well I see the vphysics crasher is alive and well after the srcds update > >>>last week. > >>> > >>>> vphysics.dll!260a2426() > >>> vphysics.dll!260d3eae() > >>> vphysics.dll!2608af8e() > >>> vphysics.dll!2608b01b() > >>> vphysics.dll!260a2697() > >>> vphysics.dll!260aac2b() > >>> vphysics.dll!2609cd5b() > >>> vphysics.dll!2609cae9() > >>> vphysics.dll!260967d8() > >>> vphysics.dll!2601d878() > >>> server.dll!22196475() > >>> server.dll!22194661() > >>> server.dll!221946c0() > >>> server.dll!22156317() > >>> server.dll!22156292() > >>> server.dll!2213d340() > >>> engine.dll!0da9e42f() > >>> engine.dll!0daa0691() > >>> engine.dll!0da9b0e7() > >>> engine.dll!0da9cc75() > >>> engine.dll!0da03cd7() > >>> engine.dll!0da04376() > >>> engine.dll!0da0f025() > >>> engine.dll!0da0f112() > >>> user32.dll!77d496b8() > >>> engine.dll!0da0f1af() > >>> engine.dll!0daacefc() > >>> engine.dll!0daac4ed() > >>> dedicated.dll!1000c084() > >>> engine.dll!0daacd4e() > >>> engine.dll!0daac48b() > >>> dedicated.dll!1000c535() > >>> dedicated.dll!1000c553() > >>> materialsystem.dll!00cd0dae() > >>> materialsystem.dll!00cd0f38() > >>> materialsystem.dll!00cd0dae() > >>> materialsystem.dll!00cd0f05() > >>> materialsystem.dll!00cd7f64() > >>> materialsystem.dll!00cd9502() > >>> tier0.dll!0087299f() > >>> materialsystem.dll!00cda349() > >>> tier0.dll!008764b5() > >>> tier0.dll!0087105a() > >>> tier0.dll!008731d0() > >>> tier0.dll!008738de() > >>> datacache.dll!00e7daa2() > >>> datacache.dll!00e7e08e() > >>> datacache.dll!00e733ae() > >>> datacache.dll!00e73e6b() > >>> engine.dll!0db556b8() > >>> engine.dll!0db552dc() > >>> engine.dll!0d9adc0d() > >>> dedicated.dll!10021d0b() > >>> dedicated.dll!10022c00() > >>> dedicated.dll!10022c00() > >>> dedicated.dll!1000c7f7() > >>> ntdll.dll!7c9106eb() > >>> > >>> > >>>At 2006/03/07 07:38 PM, [EMAIL PROTECTED] wrote: > >>>>Is there another resource that might be able to explain the recent > >>>>vphysics change in particular, or shed light on HL2's vphysics bug in > >>>>general? > >>>> > >>>>At 2006/03/05 01:28 PM, [EMAIL PROTECTED] wrote: > >>>>>It's worth noting that whatever the change was, it primarily appears to > >>>>>have gotten worse on linux. Although strangely vphysics.so crashers > >>>>>have, if anything, gotten more rare. > >>>>> > >>>>>The behavior of the bug has not changed much on Win32 it seems. Though > >>>>>again may vphysics.dll crashers have gotten more rare. > >>>>> > >>>>>At 2006/03/04 12:23 AM, [EMAIL PROTECTED] wrote: > >>>>>>Well, the mid Dec one is it then. I know I didn't update my server > >>>>>>between Thanksgiving and New Years, and the others server hosts I know > >>>>>>probably didn't either. The symptoms are the same as the same as > >>>>>>always, but the repro time frame seems to have changed like I said. > >>>>>> > >>>>>>Does anyone know what happened in the Dec update? > >>>>>> > >>>>>> > >>>>>>At 2006/03/03 09:46 PM, Alfred Reynolds wrote: > >>>>>>>Oh, and I should add that the only vphysics change in the srcds beta is > >>>>>>>a save game fix for springs (initializing a member variable properly on > >>>>>>>construction). > >>>>>>> > >>>>>>>- Alfred > >>>>>>> > >>>>>>>Alfred Reynolds wrote: > >>>>>>>> There hasn't been a srcds update since mid Dec 2005. We have a beta > >>>>>>>> update in testing now, do you mean that one perhaps? > >>>>>>>> > >>>>>>>> - Alfred > >>>>>>>> > >>>>>>>> [EMAIL PROTECTED] wrote: > >>>>>>>>> I'm getting reports that the latest srcds steam update has increased > >>>>>>>>> the amount of vphysics bugs. > >>>>>>>>> > >>>>>>>>> I'm fairly certain now there was a vphysics change. Does anyone know > >>>>>>>>> when the last one occured? It apparently has introduced more bugs in > >>>>>>>>> the srcds core. > >>>>>>>>> > >>>>>>>>> My vphysics.so is dated Feb 18 22:26 but I'm not certain if that's > >>>>>>>>> the compile time, or the install time. > >>>>> > >>>>>_______________________________________________ > >>>>>To unsubscribe, edit your list preferences, or view the list archives, > >>>>>please visit: > >>>>>http://list.valvesoftware.com/mailman/listinfo/hlcoders > >>>> > >>>>_______________________________________________ > >>>>To unsubscribe, edit your list preferences, or view the list archives, > >>>>please visit: > >>>>http://list.valvesoftware.com/mailman/listinfo/hlcoders > >>> > >>>_______________________________________________ > >>>To unsubscribe, edit your list preferences, or view the list archives, > >>>please visit: > >>>http://list.valvesoftware.com/mailman/listinfo/hlcoders > >> > >>_______________________________________________ > >>To unsubscribe, edit your list preferences, or view the list archives, > >>please visit: > >>http://list.valvesoftware.com/mailman/listinfo/hlcoders > > > >_______________________________________________ > >To unsubscribe, edit your list preferences, or view the list archives, > >please visit: > >http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
