The Nicholaz Viewer

The problem is that there are so MANY Nicholaz versions, and so many SL viewer versions.

Tell us what SL viewer software you're using, and what patch version you downloaded from Nicholaz, and what behavior you are seeing.

Yes. The Nicholaz viewers are installed over LL viewers, they don't replace them. You have to have the Official viewer installed, and then apply the proper patch.

Exactly - if you have not installed 1.18.5(3) in its own directory, you cannot run the version I am running. Trying to put my Nicholaz version over 1.19.x would not work. There is someplace where you can get the previous SL installations, although I believe only 1.18.x will work.

I believe there are links to them on Nick's site.

I am so confused with this! I want to try out the Nicholaz viewer as I have occasional crashing problems with SL. I am currently running Windlight 1.19.0. I don't really want to go back to the old viewer as I just got a new card and finally can see the pretty water effects etc.
Is there a Nicholaz version to go with this? I'm having trouble figuring it out. The latest Windlight version I can see on the blog is 1.18.something.

RL has taken priority and he hasn't been keeping up with the releases.

I want to semi-permanently install SL's client and Nick's client on the same PC. I know the programs will co-exist happily if installed to different directories. My question is about the Application Data.

The preferences are SO different for the new client than from the old BE-v version that I'm wondering if I should also use a seperate Application Data directory? I guess this is a statement of lack of faith in LL's ability to correctly version their preferences

I see a preference for where to put the cache, but I don't know if/where there is a parameter setting the Application Data location.

So, my questions:
> Is anyone running both Windlight and Nick's client on the same PC with no problems?

> If so, are you sharing the cache, or did you set up a separate one?

> If so, did you change the Application Data location? Is that even possible?

TIA
.

He did say in his last Blog that BE- should continue to work when the 1.19 series becomes "Mandatory" (tm)

I installed it last night after the disappointing results with the mandatory upgrade of 1.19.1.

Worked very well until the grid shutdown. Have 1.19.1 and BE-V in separate directories.

I'm currently using Nicholaz's BE-v with 1.18.5.3. I haven't had any problems. I plan to stick with that combination until it no longer works or Nicholaz finds the time to work on a new version.

You might want to test out the "Cool SL" viewer. It's got a lot of Nicholas's patches, as well as others. It's got an interface similar to Nicholaz, and allows you to OPTIONALLY play with "Restrained Life" if you're into that (but it's turned off by default, so no worries). It's also being "currently developed" and is available in "Standard" and "Windlight" flavours.

Links:
Linux: http://sldev.free.fr/
Windows: http://www.freewebs.com/boylane/

Hi Nika,

I have been running Nicholaz BE-v (1.18.5.3) for a couple of months. I also have various other viewers installed in separate directories at any given time and they do not seem to affect my Nicholaz viewer, and I have not done anything with the cache or Application Data at all.

But, now I wonder if I can improve performance by separating them... hmmm...

I have a number of viewers on my computer. I install the Linden viewers, copy them to a separate folder on my second hard drive, then uninstal the Linden viewer. I make extra copies of the Linden viewer if I need to. Currently I run the Beta Grid Viewer, Nicholaz Be v, Dazzle, Boy Lane's 1.19.0.5 and 1.19.1.4, and the two Linden viewers 1.19.0.5 and 1.19.1.4. I have no problems at all with this arrangement. No Linden viewer is actually installed. If anyone knows and give me instructions on how to make each viewer save its preferences in its own folder I'd be very pleased.

Aha! Thanks much then, I'll go ahead and try it! I, too, may try separating the Windlight and Nick caches just for kicks.

/me lurves teh forumz!

Hello,

i can not find the link to the original SL 1.18.5.3 viewer required by Nicholas version...

Any help?

TIA

Prez

http://nicholaz-beresford.blogspot.com/2007/12/release-bleeding-edge-be-v.html

This is the webpage for the viewer. It also has a link to 1.18.5 viewer download.

Anyone having trouble logging in using this? For some reason I can't login and I was using it earlier today.

It's not the viewer, it's SL.

I downloaded the most recent Nicholaz viewer and when i unzipped i got this error message:

Extracting Nicholaz.exe
bad CRC a6c57f63 (should be e8af8090)
Warning: the size of the extracted file (16224704) does not match the uncompressed size (16224256) recorded in the zip file

i tried downloading it three more times and each time i unzipped i got the same error message from WinZip.

I even tried another unzip program WinAce and got this error message:

Bad CRC a6c57f63 (should be e8af8090)

Can someone help me? Pleeeeeeease??

♥kisses♥
bre

I tried that OnRez viewer because someone said it fixed, what I call "Crotch-Wigs" where you hair goes to your crotch. Actually all or most of your attachments go to your crotch if you cross sim borders, while sailing, piloting, horseback riding, etc.

It seemed to work I flew several Heli's and planes back and forth in a figure eight across sim lines and my attachments never came off. But when I stopped, the viewer crashed about 5 times in a row and I havent used it since

I am going to try the Nicholaz viewer, since he is the one who supposedly submitted the fix to LL and they would not import it because they "didn't understand why the fix worked". I was the one who questioned them about it in the "work hours" transcript and got that BS answer.

Just a short note to let you know that despite earlier plans, I made something based on the 1.19. viewer which fixes the memory leak.

See http://nicholaz-beresford.blogspot.com/

@pointside: have a look at this one http://nicholaz-beresford.blogspot.com/2008/04/three-tidbits.html ... you may like the first of that

@Bre: Some people have trouble downloading from my server, try this link instead: http://download.yousendit.com/E520B0E83FA8E8AF

@All: Enjoy


Nick

LOL figures...
169 // Rather hacky, but no-one can think of something
170 // better to do for this case.

Thats great news on the 1.19 client Nicholaz



Office hours Transcript:
This is not a direct copy paste I pieced together the relevant parts.

[13:50] Ollipeist Balogh: Why do you consistently ignore the contributions of your best OpenSource contributers?
[13:54] Detour Sideways: maybe there was also an oversight evaluating his patches.
*** He has fixed ass-tachments and several leaks ***
**[13:55] pointside Sunbelter: /wait he fixed the shoe up the but, thats sim crossing tp jira? A year old or more
**[13:54] Brad Linden shouts: some of them do not "fix" the bug, they just hide it from showing up, these do not make the client more stable
**[14:00] pointside Sunbelter shouts: /I dont understand how keeping hair on your head and not at your crotch would be a hiding issue??????
**[14:00] Brad Linden shouts: pointside: it's because the way he fixed it shouldn't have fixed the issue, it still could show up, and we didn't understand why his fix should work.
[14:01] Ollipeist Balogh: Screw that, fixd for us is fixed for us. Who cares if it "shouldn't" work. It DOES!

[14:01] Kooky Jetaime: Brad, THAT IS NOT LOGICAL!
[14:02] Kooky Jetaime: Your a programmer.
[14:02] Kooky Jetaime: "It works. It SHouldn't work though. IT must be wrong." is NOT the reason to not use something.

*** I love Kooky's line "Brad,THAT IS NOT LOGICAL" because It makes me think of one of my funny pics:
http://i13.photobucket.com/albums/a259/Pointside/forums/Aint-Logical-Spock.jpg

[14:02] You shout: alright, solved or not- I have to end the Nicholasz talk-

***
Shortly after this LL posted the blog about looking for programmers. So are you going to go work for them Nick? They could sure use somebody like you, and you probably know their code as good or better than they do.

Thank you Nicholaz! I couldn't log yesterday with the regular client, went out and found your new version and got right on! Thanks again, you ROCK!

@pointside: just a bit of background ... as far as I can try to unravel that to a non-programmer (otherwise just look at the source and trace the message flow).

Let me explain what the asstachment bug was, by means of an anal-olgy (sorry for the baaaaad pun, but with asstachments was just too tempting).


When you have short power outages or spikes in the house, rebooting your computer every so often, you can

a) complain with the power company to fix their fucking nuclear plant and also check the power lines which lead to your house
b) check that the cabling *in* your house is correct and then install an USV in the basement or at least for your computer (because the short outages neither bother anyone with the lights, nor with the stove).


The asstachment problem was caused by events appearing in the wrong order (an attachment being added where one was already existing, which is impossible under normal conditions because attachments can only go into empty spots).

Now with infinite time and manpower, you can of course debug the server code, the internet connection and the viewer to make sure that such a situation doesn't occur, but for me it's sufficient if the viewer deals with unexpected conditions correctly (actually there was some kind of error handling for that situation already in place in the viewer, it just didn't handle it gracefully enough ... well, at least given the embarrasing results )

I hope this is somewhat understandable for mere humans (i.e. non-programmers )..

The Lindens love solutions with grandeur, a humble patcher like me just takes the practical and effective approach. That's the difference

And if that guy thinks that my patch *should* not have worked, it's probably because I looked at logs and debugger and dumps and such situations for a total of 15 hours and eventually knew what I was looking for ... while the Lindens weren't even able to reproduce it for a whole year. (You know: You can't fix power spikes like that with three parts from the hardware shop for $3.50, you'll at least need a XCV-2000-Series-3 with ultra-gizmo).

I admit I have made patches, which were just a bit of duct tape, because I knew the Lindens would want to do it their way anyway, so my version was just highlighting the problem and I never bitched about these patches because I didn't expect them to be accepted anyway ... and besides, you can achieve amazing things with a bit of duct tape.

But the asstachment patch was as solid as it could get without walking down and checking every high voltage power cable from your house down to the power plant (and possibly you'd need to demand entry there too).

Ahh, but anyhow ... whom am I telling this? Excuse me ... I guess I was just rambling ...


Nick


PS: Re the job offers: I'm running my own business and am happy here ... I'd only again work at a company bigger than 10 people if the alternative was starving (and I can live on amazingly little food ... we Bavarians can get along with a bit of beer for quite some time )

Well, Nick, as a person who's run a number of engineering teams, I know the argument well that says "we don't want to patch to conceal the symptom, we need to know when it's happening so we can fix the root cause". And for some really obscure issues that have big consequences, that can be valid.

But for a frequently-occurring irritant like this, most good codebase managers I know would say: put in the patch to save the users from it, comment in the code that this is a workaround, and throw a debugging event to capture info should we ever want to track it down. And MOVE ON!

Anyway.

I don't know whether you saw it, but just for kicks here is the jubilation thread that appeared when you posted last week that you were thinking of making a new version:
/327/df/253079/1.html
.