SCP Beta 2 Issue Reporting

[67510e40b1f41JML]

Awesome. Better with the walls!

[67510e40b20e6Vegoraptor]

Might be interesting to see how exactly it looks with custom water textures, since most users would use vurt's stuff I'd imagine...
Also, is that just for the pool area, or are you planning to add a similar effect to other areas like the flooded MedSci corridor or even The Many's bowels?

[67510e40b2225ZylonBane]

Research continues along those lines.

[67510e40b230dSystem Shock]

Great work ZB !

[67510e40b2420ZylonBane]

Yeah I'm thinking this experiment may be a keeper.

https://www.youtube.com/watch?v=mMNRdAz3FtA

[67510e40b2839RocketMan]

The effect looks very nice... beyond nice, but I would advise caution using it near any body of water.  The lighting conditions are a key ingredient in making this effect.  Placing it in areas that have no light sources would make the effect look out of place, as it did in the above video upon entering the corridor at first.

These caustics are a result of light originating within the body of water and light reflecting off of the surface from a nearby light source.  The refractive angle of the surface of the water changes because of the waves.  Waves produce water-air interfaces at angles to one another, which refract light either away or towards one another, causing uniform light rays to concentrate or disperse and when those rays strike another surface like a wall, they create these nice patterns.  The effect can originate from a light source in air via reflection/refraction or a light source under the water by refraction.

[67510e40b292cZylonBane]

There is a light source. That's why it's not dark.

[67510e40b2a11RocketMan]

Far as I know ambient lighting has no discrete source in dark.

[67510e40b2b85Join2]

Looks like this is coming along nicely.

My next Shock 2 playthrough is overdue. Awaiting next release.

Shit, I just remembered I've yet to play Secmod 3 too. Oh well, I'm not going anywhere, and neither are the mods, so there's plenty of time to get around to both.

Regarding the caustic effect, shouldn't it be just a tad more subtle?

[67510e40b2c8cZylonBane]

The 90s were not a time of subtle visual effects.

Though the MedSci reflections will probably be reduced somewhat yes.

[67510e40b2e01voodoo47]

to whom it may concern - the last 10 pages of this topic yielded about 100 valid issues that were subsequently fixed. I think I need a stronger word than f*ck at this point.

we will have to set serious, serious rules for (mass) beta3 issue reporting.

[67510e40b3116rccc]

to whom it may concern ...

so subtle *chuckle* scnr

[67510e40b3444System Shocked]

to whom it may concern - the last 10 pages of this topic yielded about 100 valid issues that were subsequently fixed. I think I need a stronger word than f*ck at this point.

we will have to set serious, serious rules for (mass) beta3 issue reporting.

Don't shoot the messenger. Thanks for the indirect thumbs up  voodoo47.

The stronger phrase that you need is "f*ckin details" and "THANKS AGAIN for identifying ANOTHER 100 LEGIT ISSUES that needed fixing"- SS2 still has a lot of sh@t that needs correcting, both graphically and level design wise.

I'm so happy that SS2 Beta 2 will be improved by at least 100 issues (I was hoping for far more), but if you keep digging throughout the past SS2 and SCP Beta 1 and SCP Beta 2 Issue Reporting forums, you'll find even more valid problems that can be fixed and hopefully included within the upcoming release of SCP Beta 3. You've got about 20 days left.

Sorry, but mass SCP Beta 3 issue reporting would potentially be far less if more attention was given towards fixing issues reported in SS2 and SCP Beta 1 and SCP Beta 2, way back when. In any event, I expect that all of the old and new issues that remain after the release of SCP Beta 3 will be posted onto the Google.Doc.

[67510e40b3934RocketMan]

Don't shoot the messenger. Thanks for the indirect thumbs up  voodoo47.

The stronger phrase that you need is "f*ckin details" - SS2 still has a lot of sh@t that needs fixing, both graphically and level design wise.

I'm so happy that SS2 will be improved by at least 100 issues (I was hoping for far more), but if you keep digging within the SS2 and SCP Beta 1 and SCP Beta 2 Issue Reporting forums, you'll find even more valid problems that can be fixed and hopefully included within the upcoming release of SCP Beta 3. You've got about 20 days left.

Sorry, but mass SCP Beta 3 issue reporting would potentially be far less if more attention was given towards fixing issues reported in SS2 and SCP Beta 1 and SCP Beta 2, way back when. In any event, I expect that all of the issues reporting will be posted on the Google.Doc.

It may be a novel concept to you but your idea of what constitutes a valid concern is NOT absolute truth, like 1 = 1.  It is subject to dissection and rebuttal.  And since you're not doing any of the work to fix any of these issues, a simple veto is fully sufficient from anyone who is fixing them.  You must accept that without complaint.  As for your countdown timer... you really don't know when to quit.  Nobody is on your schedule.  Get it through your head.  We don't work for you.  If you gave V47 and ZB 40k a piece right now, I suspect they still wouldn't accept you as their boss in any case so quit the managerial persona for the billionth time.  It reeks of superiority and disrespect.

[67510e40b3aeeKolya]

System Shocked had been banned from posting for quite some time which is why we hadn't heard of him. The reason for his ban was of course what you describe aptly as his "managerial persona". And if it was for me, he would have stayed banned indefinitely. But v47 and ZB said they missed their little punching bag. So regardless of the hilarious demands he will continue to make, that is his karmic role, his raison d'être, his purpose in our world.

[67510e40b3c1avoodoo47]

I'm pretty sure everything that could be said has already been said, so lets try to not have this conversation again.

though I do want to add that seeing reports of things that have been fixed long ago in the future beta3 issue reporting topic will make me.. grumpy.

[67510e40b3d55RocketMan]

I apologize.  Consider the matter closed from my end.  I guess I just let him get on my last nerve.

[67510e40b3e36ZylonBane]

It's fine. We have yet to determine whether he's actually capable of human thought and emotion.

[67510e40b3f12voodoo47]

as long as he'll be able to follow a few basic (beta3 issue reporting) rules, I don't really need to know.

[67510e40b496dSystem Shocked]

It may be a novel concept to you but your idea of what constitutes a valid concern is NOT absolute truth, like 1 = 1.  It is subject to dissection and rebuttal.  And since you're not doing any of the work to fix any of these issues, a simple veto is fully sufficient from anyone who is fixing them.  You must accept that without complaint.  As for your countdown timer... you really don't know when to quit.  Nobody is on your schedule.  Get it through your head.  We don't work for you.  If you gave V47 and ZB 40k a piece right now, I suspect they still wouldn't accept you as their boss in any case so quit the managerial persona for the billionth time.  It reeks of superiority and disrespect.

Your past assumptions are completely misguided:
a) I've never asked to or to be considered a SCP Dev. ALL of my entire efforts to date have been to ID and suggest fixes within SS2, SS2 Beta 1 and SCP Beta 2, and the lack of design/visual discrepancies within a level or from one level to another.
b) "And since you're not doing any of the work to fix any of these issues" . . . . . HOW can you've not noticed, based on my massive issue feedback reports, that I'm not a fixer of problems, but have always been a reporter of problems ??? ANYONE would think by now, that I'm not a fixer of problems that exist within SS2, but can only consider me as an identifier of problems that still exist within SS2, SCP Beta 2 and SCP Beta 3.
c) After an extended period of time, a dedicated issue reporter hardens his/her position/dialogue after a number of certain obvious game deficiencies aren't considered/addressed and fixed. This escalates the entire correction process. Can't do anything unless given a reasonable excuse.

System Shocked had been banned from posting for quite some time which is why we hadn't heard of him. The reason for his ban was of course what you describe aptly as his "managerial persona". And if it was for me, he would have stayed banned indefinitely. But v47 and ZB said they missed their little punching bag. So regardless of the hilarious demands he will continue to make, that is his karmic role, his raison d'être, his purpose in our world.

It's truly sad that a dedicated forum member that has devoted so much of his time/efforts and has submitted 1000's of SS2, SCP Beta 2 and SCP Beta 2 feedback reports is so disrespected/unappreciated.   
a) I'll strongly state again, "I've never asked to or to be considered a SCP Dev. ALL of my entire efforts to date have been to ID and suggest fixes within SS2, SS2 Beta 1 and SCP Beta 2, and the lack of design/visual discrepancies within a level or from one level to another."
b) [/quote] But v47 and ZB said they missed their little punching bag. So regardless of the hilarious demands he will continue to make, that is his karmic role, his raison d'être, his purpose in our world.
[/quote]
REALLY ?. . . REALLY ??? . . . . . So, I'm considered to be nothing more than a punching bag??? The real truth is that you SCP Devs NEED me around . . . . . my feedback probably resulted in about 350 issues being fixed within SCP Beta 2 - SCP Beta 3, upon its release at the end of this month. Based on my previous efforts/observations/submissions, the SCP project would be about 750 issues in arrears, if not reported by myself. You SCP Devs need to recognize that NO-ONE else, for an extended period of time (hardly ever) has been submitting ANY issues found within SS2 and thereafter. I'm your only feedback option going forward. It's not likely that anyone else will step forward.

It's fine. We have yet to determine whether he's actually capable of human thought and emotion.

Hey ZBane, don't shortchange my importance. You have a seminal game that you're trying to improve, but NO-ONE has submitted any ongoing appreciable issue feedback reports. Like it or not, at this point in time, I'm your only ticket in town. Nevertheless, I'll give you the honest feedback and support that you deserve.

[67510e40b4a6dchickenhead]

Oh my GOD.

[67510e40b4cf2voodoo47]

I'm pretty sure everything that could be said has already been said, so lets try to not have this conversation again.

though I do want to add that seeing reports of things that have been fixed long ago in the future beta3 issue reporting topic will make me.. grumpy.

also, don't overestimate your importance.

[67510e40b503aSystem Shocked]

to whom it may concern - the last 10 pages of this topic yielded about 100 valid issues that were subsequently fixed. I think I need a stronger word than f*ck at this point.

we will have to set serious, serious rules for (mass) beta3 issue reporting.

To aid in the reporting/tracking/fixing of issues within SS2, the introduction/implementation of the Google.Doc issue reporting system was established. The creator of the document thankfully loaded it with a limited history of recent SS2 issues reported from within the forums, but far from all.

The SCP Devs have updated the "fixed" status on some of the reported issues, but far from all, most likely because the Google.Doc reporting system is in flux.

It seems that the status of issues reported within the SCP Beta 2 issue reporting forum have fallen by the wayside. Since the introduction of the Google.Doc issue reporting system, it hasn't been kept up to date. Just recently, the Google.Doc has been updated by Voodoo47 to reflect that a half-dozen eggs will be fixed so that they emit their missing murmuring sounds within SCP Beta 3. That's great, and a long time coming.

However, Voodoo47 recently announced above that "about 100 valid issues were subsequently fixed" within SCP Beta 2. These fixed issues should be updated to the Google.Doc so that the SS2 community can understand which levels these issues exist and their approximate locations and what types of issues have been fixed. This info allows issue reporters to focus within certain types of issues, levels (scripted/unscripted) in order to search for additional valid new issues.

[67510e40b5139ZylonBane]

Take your meds.