 |
The code for setting up lightgem is in function R_Lightgem_Render. I believe right now it always uses eye position as lightgem location. There is some logic to put to put location 30% between normal origin and leaned position, to adjust for crouching, etc. But right now it is not used. I guess all of it was broken during changing how lightgem works in terms of rendering (maybe 2.05?) So I would say that: 1) Use the LGPos as origin for lightgem subview rendering (lightgemRv.viewOrg). Check that lightgem works properly and nothing is broken =) 2) Make sure peeking does not modify lightgem position. I think as soon as p.1 is fixed, lightgem will behave properly while peeking. 3) Preferably move the whole stuff about lightgem position calculation into a method of idPlayer class. It is strange that frontend code contains this obviously gameplay logic. |
|
|
Here is restoring back LGPos. However, there are many more problems: 1) Moving mouse in peeked view is inverted horizontally from one side of the door. 2) It is weird that moving mouse around causes camera to slide along the door plane. At the same time, view direction is not orthogonal to this plane. The math and controls for peeking view need some love, that's for sure =) 3) I still get dark lightgem when peeking into a door from bright side. Moreover, I get dark lightgem when peeking even if there is strong light on both sides of the door. tr_subview.cpp.patch (508 bytes) |
 |
Hm, that is strange you are seeing a dark lightgem when looking into a lit room. Admittedly, I haven't really looked at this since I first reported this for Seeking Lady Leicester, but I'll do some testing later. Maybe something has changed? |
|
|
So I tested using func_peek in the 2.12 release build, and I am still getting this lightgem glitch. It's puzzling why you aren't able to replicate this. For me, the light gem changes slightly. Try this door in SLL: seekinglady (2024-03-16 12-26-08) (2580 642 41).jpg (140,796 bytes) |
- Anonymous
