 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Fixed Bugs:
HOMS through walkways at odd angles Zfighting inside door frames Unmarked / broken secrets Crash on easy skill Items falling out of level New Stuff: Added coop starts (untested) Added dirtmapping Added brushes to better divide the visleafs (performance) Added some dynamic helper signs to aid navigation Various miscellaneous tweaks and gameplay fixes Thanks for the file inclusion Jakub - I'm kind of surprised it runs at all in DP, just for the custom gameplay Qc - mainly the ammo boxes. The corners more shadowed but not affect the gameplay areas.
Some secrets are a bit darker now. i tested the whole pack and even monster level like telefragged works fine in darkplaces. i encountered noticeble fps slowdown only in the incenerator area. other parts of the level were ok.
- there was only one bug i found. in telefragged, there is a secret quaddamage behind the glass door that can be opened by shooting the button on the floor through the crack in the nearby window pane. the button is inaccesible behind the glass under the crate at first and when the crate explodes the explosion cracks the glass so that you can shoot the red button on the floor. the crate explodes and cracks the glass, but the button doesn't work. it worked in the original version, but doesn't work in the updated version released a few weeks ago. i haven't tried the new version yet. Will take some today.
As to that secret - I tested it last night and it was fine, but in Quakespasm. i'll try it again with the new version when i get home. the button is already in the "pushed" state when the glass cracks so that you can't shoot it again.
"incenerator = incinerator :-) "
Thanks for that correction. I had NO idea what you were trying to say there These are the dropbox links:
Here's the patch (bsp + lit): https://www.dropbox.com/s/2lk84vnzy3oeaeo/rrp_patch103.zip?dl=0 And here's the full patched download: https://www.dropbox.com/s/5xzckbmk99yz8mp/rrp_v103.zip?dl=0 And here are some screens: http://www.quaketastic.com/files/tfraggedv103scr1.png http://www.quaketastic.com/files/tfraggedv103scr2.png http://www.quaketastic.com/files/tfraggedv103scr3.png http://www.quaketastic.com/files/tfraggedv103scr4.png http://www.quaketastic.com/files/tfraggedv103scr5.png http://www.quaketastic.com/files/tfraggedv103scr6.png http://www.quaketastic.com/files/tfraggedv103scr7.png Can a mod add these to the header please? Keep in mind Barnak is using a non-Intel Mac Mini and no modern browser is available for him to use.
I'm sure the patch will get mirrored to quaddicted or quaketastic before long.
Barnak, try using Firefox or Chrome on OSX 10.6, not Safari (which is out of date and probably unsafe). If folks are in the business of updating the OP, you could remove the link to the special-snowflake devbuild of Quakespasm and just say "use Quakespasm version 0.90.0 or later".
I'm able to download the pack by turning the URL from =0 to =1.
At least, make that download button to play a fart sound when you press it. I'm experiencing a video problem with both versions of Rubicon3 when FSAA (antialiasing) is ON, in the latest version of Quakespasm OS X.
Rubicon3 is the only Quake pack/mod/map which is giving me video garbages when FSAA is ON. This is sad, since FSAA is nice to my eyes, and I need to turn it OFF just to play Rubicon. Why is there a problem with FSAA and this mod ? A screenshot for the Quakespasm would be the considerate thing to do wouldn't it?
Or shall they just guess what your screen looks like I was about to ask for a screenshot but I can reproduce it on my OSX 10.6 system, a HOM effect, but some parts of the world draw?
It affects id1 start.bsp too though, so it's not specific to RRP. Seems to be related to the waterwarp, setting "r_oldwater 1" works around the problem here. What are the differences with the oldwater settings ?
And what is specific to Rubicon3's water, that is different from the other water settings, in AD for example ? Rubicon is the only Mod that gives me screen shit when FSAA is ON. The screen shit looks like transparent walls, with a very luminous background (sky box), that blinks when I move the view around. The game becomes unplayable with this. It affects how the waving animation on the surface of liquids is drawn.. "r_oldwater 0" is the better quality way, but it can cause problems with buggy OpenGL drivers. "r_oldwater 1" is more compatible but looks more angular.
There's nothing specific about RRP, but maybe the quake.rc forces "r_oldwater 1" which triggers the bug for you. Argh, I meant "r_oldwater 0" the last time.
Anyway - assuming you are having the same issue as me, setting it to "1" should work around the issue for now. I'll see if there's any straightforward way to work around it in the engine. "new water" in fitzquake/quakespasm uses the framebuffer as a scratchpad to draw the waterwarp, then copies that into a texture, then draws the scene for real. Perhaps there's some driver/hardware issue that makes copying framebuffer to texture give bad results. "Old water" uses the glquake method, which is safe but ugly.
Ideally it would all be replaced with a fragment shader :) It's a little crazy that FSAA has to be on for Barnak's issue to manifest itself.
@ericw --- gl clear happens AFTER warp textures are updated --- metlslime probably figured better to do it before clearing buffer. Perhaps gl_clear before and after would solve issue if FSAA is on? (You wrote a dev note saying some Intels need the buffer always cleared. Barnak's computer is saying "Hello!")
|
|
|
Post A Reply: |
|
| Website copyright © 2002-2017 John Fitzgibbons. All posts are copyright their respective authors. |