How to turn off sub reflections?

[onelifecrisis]

Originally Posted by ref

We didn't "introduce" anything, and there where no missing conning tower reflections, just the periscope and Sergbuto did the fix a long time ago, please be more carefull and try to investigate a bit before saying someone made a bug...
And please post a screenshoot of your problem, the graphic problem you mentioned has nothing to do eith reflections viewed from the conning tower.

Ref

Try to investigate a bit?

I've been searching/reading these forums for several hours a day for months now. As much as you'd like to think that finding out what fixes what and what breaks what is as easy as hitting "search" the reality for newcomers like me is a far cry from that. Generally I find nothing at all or hundreds of posts including multiple conflicting opinions on any given topic. I am pretty sure GWX introduced this but if I'm wrong, consider me corrected on my facts - but not my approach to finding them.

[onelifecrisis]

Okie dokie... a little searching (I'm now an expert forum searcher) reveals that Sergbuto did a mod called U-boat Reflections V2 in 2005, which added various reflections, including the conning tower and periscopes, thus creating the problem you refer to. It is my assumption that this mod, or a version of it, is included in GWX, since GWX also adds these reflections.

Am I barking up the wrong tree here, or is it in fact you, Ref, who needs to do a little more research before posting?

[TheDarkWraith]

Open the file in question in a hex editor and search for WaterReflections. Under that will be a sub-heading called 'Reflections'. Change the byte from 1 to 0 to disable that relfection that the ID refers to. If you set all these to 0 then you disable the reflections.

[onelifecrisis]

Originally Posted by Racerboy

Open the file in question in a hex editor and search for WaterReflections. Under that will be a sub-heading called 'Reflections'. Change the byte from 1 to 0 to disable that relfection that the ID refers to. If you set all these to 0 then you disable the reflections.

Ah, okay, thanks for the help (time for me to try to work out how to use this free hex editor thing )

Cheers Racerboy

[Kpt. Lehmann]

Originally Posted by onelifecrisis

I am pretty sure GWX introduced this but if I'm wrong, consider me corrected on my facts - but not my approach to finding them.

Not only are you wrong about the problem you claim was introduced by GWX... but you have misquoted what was said.

If you need shovel to dig yourself out of the hole you've made... just let us know. We'll be happy to give you one.
Think before you post.

[onelifecrisis]

Originally Posted by Kpt. Lehmann

Not only are you wrong about the problem you claim was introduced by GWX... but you have misquoted what was said.

If you need shovel to dig yourself out of the hole you've made... just let us know. We'll be happy to give you one.
Think before you post.

Misquoted what? I just hit the quote button - I didn't edit it. Are you now saying that the forum quote button is as faulty as my information?

If I'm wrong I'm wrong, but as I said and will say again, it's not for lack of trying to find out what the facts are before posting. I never noticed this graphical problem before GWX and seeing as (according to the thread by Sergbuto, and his website, both of which I found thanks to Ref) the reflections in question are not in stock, I think my reasoning was perfectly sound. Furthermore my original comment, as quoted by Ref, was "I think that GWX introduced this problem", and my offense to Refs post was in reaction to his accusation that I had not done enough research, rather than his statement that I had my facts wrong - as I'm sure you'll see if you read my reply.

No need for a shovel as I don't see that I'm in any kind of hole, but if you like to imagine yourself looking down on me, knock yourself out.

[Kpt. Lehmann]

Originally Posted by onelifecrisis

Misquoted what? I just hit the quote button - I didn't edit it. Are you now saying that the forum quote button is as faulty as my information?

If I'm wrong I'm wrong, but as I said and will say again, it's not for lack of trying to find out what the facts are before posting. I never noticed this graphical problem before GWX and seeing as (according to the thread by Sergbuto, and his website, both of which I found thanks to Ref) the reflections in question are not in stock, I think my reasoning was perfectly sound. Furthermore my original comment, as quoted by Ref, was "I think that GWX introduced this problem", and my offense to Refs post was in reaction to his accusation that I had not done enough research, rather than his statement that I had my facts wrong - as I'm sure you'll see if you read my reply.

No need for a shovel as I don't see that I'm in any kind of hole, but if you like to imagine yourself looking down on me, knock yourself out.

"Kpt. Lehmann more or less told him that they don't have time for graphical stuff"

Remember that?

Furthermore, its not the first time you've been overly sensitive regarding a posting by GWX devs.
http://www.subsim.com/radioroom/show...5&postcount=12

Or shot your mouth off without thinking:
http://www.subsim.com/radioroom/show...8&postcount=11

No one is looking down on you. We are just responding to thoughtless remarks.
It doesn't matter who or what you are... a whine is just a whine.

[onelifecrisis]

Ah, that misquote. I believe I confused your twice-made comment "dunno if we can do anything about it" in the (apparently mis-titled) thread GWX Scope Reflection with the comment "honestly, the environmental stuff is the least of my concerns... just letting you know" which you sent me via PM at around the same time (in a discussion about a possible fix for an environmental graphical error). Apparently, searching and reading the forums as much as I do on as many issues as I do is proving too much for my memory to handle.

Anyway, it's evident that the real cause for concern is rather GWX-specific, so I'll be careful not to mention the word GWX next time I'm trying to find a fix for something.

[Kpt. Lehmann]

Best o' luck to ya lad! If you insist on saying that GWX introduced those problems... You are only twisting words to meet your desires of the moment. As you show your colors here:

Originally Posted by onelifecrisis

Anyway, it's evident that the real cause for concern is rather GWX-specific, so I'll be careful not to mention the word GWX next time I'm trying to find a fix for something.

FACT: The problems you describe are holdovers from STOCK SH3. Just because we modify a file or data set... doesn't mean that we modified everything in that file.

[onelifecrisis]

Originally Posted by Kpt. Lehmann

As you show your colors here:

FACT: The problems you describe are holdovers from STOCK SH3. Just because we modify a file or data set... doesn't mean that we modified everything in that file.

When I said that the real cause for concern is GWX-specific I was not referring to the bug; I was referring to the cause of your concerns, namely my accusation that GWX *might* have caused the problem, and as I said I shall be careful in future not to suggest that this is the case, with this problem or any other.

In other words I have vowed to respect the request that both you and ref have made of me in this thread.

Are we clear now?

[onelifecrisis]

Originally Posted by Kpt. Lehmann

Best o' luck to ya lad! If you insist on saying that GWX introduced those problems... You are only twisting words to meet your desires of the moment.
FACT: The problems you describe are holdovers from STOCK SH3. Just because we modify a file or data set... doesn't mean that we modified everything in that file.

I just had to dig this thread up cos I just reinstalled stock (need stock files for a mod I'm working on) and the problem isn't there. Then I installed GWX over stock, and voila - the problem returns.

So, I was right all along! Damn, I don't even know why I listen to you guys.

If you want screenies just see that (correctly named!) "GWX Scope Reflection" thread.

This will likely be ignored but I'll ask anyway - is it going to be fixed in 1.04?