forli Posted January 16, 2016 Share Posted January 16, 2016 "except for situations with heavy lags" > this is strange: lags or not, an handler should be called in the moment the "knockout" event occur (just before the game set the knockout event). Surely, the event is fired after the OnHealthDamage, but I wonder if the game has a chance to register the Player "death" (death by knockout, which mess up the camera anyway) before firing the OnKnockout event. After all, scripts all run in a single thread, so the order of the calls should stay consistent in every run, no matter the FPS. Very odd... Anyway, Oblivion Reloaded fixes the camera bug. Link to comment Share on other sites More sharing options...
ProgMath2 Posted January 16, 2016 Author Share Posted January 16, 2016 (edited) I was wrong about the problem and it seems about the lags too.It appears that in First Person knockout event does not occur at all. That is probably what I've taken for the lags interfering the event. I was testing it mostly in TP to easily highlight player in console.So now in third person everything is working fine, but in FP camera just slowly lies to the ground and nothing at all happens. Not even getting up from unconsciousness. And only when I roll the mouse wheel, the death anim plays and the knockout script starts.Of cource, the normal damage recieving can be easily handled via OnHealthDamage in any camera mode, but catching the "kill" command in first person is still an opened question. Edited January 16, 2016 by ProgMath2 Link to comment Share on other sites More sharing options...
forli Posted January 16, 2016 Share Posted January 16, 2016 (edited) I made some tests: normally the camera is automatically switched to first person (and knockout event/timer runs) if the Player dies, but it seems OR prevent this, when CameraMode is disabled.With CameraMode enabled everything is normal (and the camera doesn't drop at player's feet). Edited January 16, 2016 by forli Link to comment Share on other sites More sharing options...
forli Posted January 16, 2016 Share Posted January 16, 2016 Issue reported on the OR thread. Link to comment Share on other sites More sharing options...
ProgMath2 Posted January 16, 2016 Author Share Posted January 16, 2016 (edited) froliPersonally, I don't use OR respecting the advanced age of my computer. I knew about that feature (my friend Google told me), but was too lazy to analyze such a global thing. I'll start now.I don't think that it can be called a bug when it works like in Vanilla, especially when when they say straightly: "It's fixed only with the Camera Mode on". But I appreciate your effort.On the other hand, if they'll do something plagiarizable, it would be very nice. Edited January 16, 2016 by ProgMath2 Link to comment Share on other sites More sharing options...
forli Posted January 16, 2016 Share Posted January 16, 2016 You can use OR with any PC. The effects impact the performances, but the shaders override don't (or the impact is barely noticeable). Just disable the heavier effects (or all them) to run the mod on an older PC.I have an hold PC too and OR runs without problems, and without loss. OR comes with a frame rate manager, which is much more advanced and effective than Streamline and similar mods, because OR directly manage it in the game code, and bring support for RamDisk, to eliminate (or greatly reduce) stutters caused by LOD files.Finally it comes with many little optimizations and fixes like the camera bug, Yeah, I removed the part "camera drop on feet", as Alenet clearly state it's only for CameraMode. Link to comment Share on other sites More sharing options...
ProgMath2 Posted January 20, 2016 Author Share Posted January 20, 2016 forliIsn't that "Camera Mode" a state of using third person animations in first person? When torch is waving in the damn middle of monitor? I trided it and I didn't liked it. I'll think about using the mod for graphics though. Anyway, I've made a mod that suits me. It combines all that I was mentioning with addition of forcing third person in vanilla cases of player.kill. So now the only bad case is non-vanilla kill in FP, and it will only make a little inconviniency of save-load to fix the camera. A shame that we could not find a universal solution, but my variant will do for me.Thanks, DrakeTheDragon, lubronbrons, forli. Link to comment Share on other sites More sharing options...
lubronbrons Posted January 20, 2016 Share Posted January 20, 2016 you're welcome :) it's good you have found your own solution, even it is not perfect at least suits your need Link to comment Share on other sites More sharing options...
DrakeTheDragon Posted January 20, 2016 Share Posted January 20, 2016 You'd be surprised (or not) how many less-than-perfect solutions with up to today still open holes and flaws there are even inside the Vanilla game code. Sometimes an as-close-as-you-can-get approximation to your perfect idea of a solution will be all there is to get really. :thumbsup: Link to comment Share on other sites More sharing options...
Recommended Posts