Disclaimer

This is MY Viewer, i decide which feature i want to add and which to remove, i share this Viewer to show the world that user base size is not important, i do rate quality by effort, thought and love put into the project, not some rough estimated numbers. I consider feature requests only if i you can name proper valid reasons i can agree on. It is my unpaid time i'm putting into this project, i'm not here to cater to every Joe's desires.

Friday, September 15, 2017

Black Dragon 64x - Alpha 3 "Bit Dragon"

So after 3 failed and missed upload attempts i'm just uploading update 3 instead. Have fun, tiny changes, most important for you is the fixed named of the executable. Other change is i removed the internal texture/scene memory limits, you can go beyond 1992m now but only in debug settings for those that want to test it out. If you do so please keep a VERY CLOSE look at your framerate and report if it has any impact on your framerate. Thanks.

Thursday, September 14, 2017

Black Dragon 64x - Alpha 2 "Bit Dragon"

So this is it.

The final update before i vanish forever into the depths of Divinity: Original Sin 2 which is about to release today. My last words are:

This update disabled HTTP Pipelining until LL figures out how to not make it blow up the Viewer and it also includes some improvements to shadows in hopefully every possible situation but most importantly on high altitudes. Shadows should flicker less if at all and they should be almost as precise as on the ground now while the ground shadows should be slightly more precise on distance too, yay for less disconnected shadows!

I hope you value this improvement as much as i do.

I think the following two comparison pictures of a theater on 1800m altitude speak for themselves.

Last update

This update

Note these are 4k shots with 6k and 4k shadow resolution to show the effect even more. They do a big improvement on normal 2k shadow resolution too. Don't believe me? Normal 1080p shot with default shadow resolution below.

Last update

This update


Much better isn't it? All those ugly free floating totally disconnected shadows. I know this is still not perfect but its basically 10 times better than anything we've ever had in SL so far and probably close to what advanced shadowing technologies would achieve.





I realize that these snapshots are partly extreme tests, i think most of you have probably seen what happens when you set a sunset/sunrise (long shadow) like preset, right your shadows will go super nuts, disconnect, vanish completely (on LL Viewer sunset basically has no shadows whatsoever), its absolutely crazy how they break in these conditions and as you can see they perform absolutely fine now.

Have fun.

Also, sadly still no launcher... still trying to figure this monster out.

Tuesday, September 5, 2017

Black Dragon goes 64bitssssss

After painstaking 5 days, compiling the Viewer up and down, back and forth and trying to find the issue, i finally, randomly stumbled upon the solution by "trying something really stupid". Needless to say stupid sadly wins. I managed to compile the Viewer as 64bit executable, with sound and texture decoding intact.


You can download the 64bit version on the usual downloads page of bitbucket. Please not that this 64bit version is absolutely the same as the 32bit version except that it is now obviously 64bit. From my tests so far however i can tell you that it runs a lot faster (for me) than the 32bit version ever did. I'm talking about 20+ more fps on the above picture's place and 10-20 more fps in the place on the picture below.


This is a drastic improvement, make sure that texture loading is done before comparing your fps, while textures where still downloading i got roughly the same low 10 fps but when they were done loading i went up to rock solid 25-30 fps. That's with deferred, shadows and SSAO on.

This build also rips out the updater system which allows the Viewer to start up faster, login a bit faster and eliminates the freeze whenever you open Dragon - Help - About Black Dragon. However, this build doesn't come with the launcher nor updater, i'll have to reconfigure them for Black Dragon soon so they'll keep it updated, so you'll have to update it manually for the time being until i can get the launcher working and can verify that its updating the Viewer properly.

For now however i'll need some rest. A lot of rest. 5 days nonstop headache trying to fix this mess just so it turns out it's a "stupid thing" that fixed it. Ugh. Oz. Get your goddamn documentation together. If you had like written one single sentence, one simple "note that 64bit libs are named after their 32bit counterparts while the dll's are named 64 as usual" all this mess could have been skipped. Or at least give us some sort of insight into your building process for the libraries like fmodex because as you may know OR NOT, we can't look into them because we cannot get them, we have to build them ourselves, which if there is no documentation on how to actually build them, is a bit hard, you know.

Thanks to everyone who tried to help me solving this shit. Specifically Whirly, Nicky, Henri and Cinder. You might not have actually helped but at least you tried, that's what counts. Also thanks to my dad who installed all this crap to look into it just to fail as i did, he did a good job at mentally and morally supporting me with his failed attempts.

Thursday, August 31, 2017

Black Dragon 64bit

I suppose i have to make an announcement for this, right?

Most of you know that several TPV's exist in both 32bit and 64bit versions, i think it should be quite obvious why 64bit, it's ability to use 18,446,744,073,709,551,616 bytes of memory, that's 16 exabytes, of course it will never use that much, to use that much you'd first have to have that much memory available physically but it boils down to one important thing, it can use more than the 3,6gb a 32bit application can use after which it will crash due to running out of memory.

Why is this important? Over the past Second Life has undergone some changes, most of the content changes have undergone absolute devastatingly bad changes, many creators in Second Life are not skilled enough to produce optimized content, whereas optimized would be something that is not absolutely terrible, so it's kinda dumb to say they are not skilled enough because making this kind of "optimized" as in not complete shit you really don't need to be skilled at all, you just need to have an idea what's good and what's bad for the client/server which is sometimes really obvious and sometimes terribly easy to test, i think it should be no secret that one avatar eating up 20mb of script memory is bad in comparison to one that uses 0.1mb, right, especially if the SIM has only a small amount of available memory. So... because lots of content has inevitably made as turn for the worse, memory usage has increased drastically, we've reached a spot where one avatar can use up to 400mb and more of your precious 3,600 available megabytes, that is 1/9 of your max, now add the Viewer which depending on which you use and the settings you use can easily take up to 400-600mb by default not taking your avatar and the rest of the region you are on into account, we're talking something around 800mb is pretty standard, that's me plus Hippo Hollow region and my high graphic settings plus some chatting on Black Dragon. It's not much isn't it? Yea but not everyone carefully optimizes his avatar like me, whenever i go anywhere the memory usage will quickly ramp up to 1.5 - 2.0gb, sometimes just for the region, that's a lot for nothing, add some unoptimized avatars on top and you'll get 3.6gb easily, resulting in a quick crash.

This has sadly become not a rare occurrence but something more and more people keep reporting me, obviously blaming it on the Viewer. I went there, checked out the region and surprise, the region alone eats almost 3gb memory, every single avatar eats like 400+mb, doesn't surprise me you're crashing here coming from Firestorm (presumably 64bit). Now i could tell you that adopting 64bit early was a big mistake which basically just worsened and sped up the moment this was going to happen, because 64bit makes people again careless, they can just use and spam whatever they want, bloating your memory without care, this doesn't affect 64bit Viewers much but does a lot of harm to 32bit Viewers such as mine and the LL Viewer, which along the fact that 64bit was necessary at some point anyway, was probably the reason LL decided to tackle 64bit and will soon become the baseline Viewer.

With 64bit becoming baseline, Black Dragon will also finally get a 64bit version, which should eliminate out of memory crashes, once and for all. That is until you run out of real memory, but don't worry, knowing Windows it will probably start freezing and possibly BSOD long before the Viewer has a chance to report out of memory and crash. Great i can see it coming, people complaining at me that my Viewer bluescreens their PC.

I'm currently in the process of trying out the 64bit compile process on a Virtual Machine with Windows 7 64bit Home Premium installed, the wiki is very vague and makes it sound like Windows 10 is required to do so and no one else i asked compiled it under Windows 7 so i was on my own (as always) working through the still incomplete guide that is the step by step article on the Wiki. Needless to say that if i get it up and running we'll soon see a first 64bit version of Black Dragon, which will end support for 32bit systems, yes that's right, no more 32bit versions. Why? You shouldn't be using 32bit anymore. It's 2017, 64bit shouldn't have been around anymore since Windows Vista sometime around 2007. I'm not Linden Labs, i won't be hand holding your outdated systems like they do hoping you will someday finally switch to 64bit which of course you will never do because we all know how that works out right? ~ "Never change a running system".



What else? ... right... i changed Auto Alpha Masking in the last update, i'm absolutely super sorry about breaking your stuff but the truth is your stuff was broken already, you just never noticed because this hack of a feature which was presumably made to have some sort alpha masking was made prior to Materials, which allows us to set the alpha mode ourselves. I feel like since Materials is here for quite some time now this hack is no longer needed and should be disabled by default, i know no one except me has the balls to do it (as always) because ohno you break content (no you fucking don't) and fixing this is as easy as editing the object or prim or face in question and setting its Alpha Mode to "Alpha Masking" if it requires some sort of alpha, like hair or cutting off legs or clothing layers or something (which really shouldn't exist in the first place) or simply "None" to get rid of the alpha completely, both Masking and None are almost identical with the exception that Alpha Masking can still have transparency but only full transparency (100%). The optimal solution would be removing the alpha channel in the uploaded texture, which most of you probably can't do but it's something you should tell your creators if you want them to improve their stuff and if they want to argue with you, send them to me, i'll give them a lecture as to why they should do it, apart from it being like 2 clicks in GIMP to remove the alpha channel (not sure in PS).

Anyway, if you for some reason can't change the Alpha Mode because you are one of those poor souls who buys overpriced human stuff which usually comes without mod permissions you might want to go into the main menu - Dragon - Develop - Rendering - Automatic Alpha Masking (Deferred) and enable that to revert to the old settings where you see your broken stuff less broken but still broken with pixelated shadows, missing SSAO, broken transparency in Volumetric Lighting and so on... but at least your hair won't poke through the front of your eyes from behind right?

That's it for today, will see you possibly on a 64bit Black Dragon soon... oh and, if for some reason 64bit turns out to be not compile-able for whatever stupid reason and i can't get it fixed, no more Black Dragon when 64bit becomes baseline. Dropped the bomb there, did i?

Saturday, August 19, 2017

Forget about update 2.8.0.

Download 2.8.1 instead! More fixes. More stuff. More ... more! Soon mandatory (which will fix the auto updating process which currently fails due to md5 hash mismatch (probably... it should))

Friday, August 18, 2017

Redownload the update 2.8.0.

Everyone who downloaded the update prior to this post please redownload the update... i missed a tone mapping setting and now everything looks darker than it should...


EDIT: Please download the update manually. I broke the updater. Grlrlrlrllll.

Wednesday, August 9, 2017

Endless Update Loop.

UPDATE: The issue should now be resolved. Let the update downloading commence.

Tuesday, August 1, 2017

Black Dragon Update 2.7.9: Posing for a cleanup.

Almost a month passed without me doing something, gotta fix that.

Updated the poser (again), now you can toggle bones on and off (will be saved into presets) and you can finally use the first iteration of the Animator, allowing some basic pose-chaining to create fake-animations.



You might also enjoy the little... thingy i did in my login screen. I might be using this to some extend in the future, to preview features and changes.



Other than that not much more, you can now toggle world lights, your own attached lights and other people's attached lights independently from each other (WOW).













I also added an option to toggle projector light projections off, again independently from their image reflections and projectors themselves.













Also... i love posing with the poser, you can do all the things, really.







Monday, June 12, 2017

Black Dragon Update 2.7.7: The performance update.

You have been waiting for this for over 5 years.

The ultimate update is about to unleash upon you.

Upwards of 3 quadrillion FPS increase. That's two fish more than tomorrow.
Every graphical feature ever, at no additional performance cost.
All lag SL ever had, fixed including 0.1ms ping for that ultimate shooter feeling.
Oculus Rave Support
And if you thought it can't get better, IT WILL GET BETTER. ALL OF THIS FOR ONLY 9.99€! + Season Pass for the next update. Dayum, what a deal.




Okay no seriously. I thought i should probably optimize stuff a bit, never done this in the past 5 years of making the Viewer so over time the framerate become somewhat unstable. framerate stability should be massively improved and you might even see some FPS gains, i went up from 40 to 60 on my place and for the first time since Nirans Viewer i managed to get 100 FPS again in the sky and even up to 180 FPS if i took off my Avatar, that's even 20 fps more than the maximum i ever managed to get. You will also see the performance impact of the sidebar being pretty much 0 now, preferences has been MASSIVELY improved too, reduced it's refresh calls massively and optimized them quite a lot, so even with preferences open you shouldn't be dropping too hard anymore. Turning around and generally doing stuff doesn't incur too much framerate dips anymore either! Whew.

Further i've also fixed some bugs, added an "always render friends" option, made highlight friends default, finetuned Tone Mapping further, clamped the view angle in sidebar, made ESC disable third person steering in case you accidentally enabled it, improved all preferences warnings and changed the visibility condition of some of them to ones that make more sense and are a bit more forgiving.

To summarize this update: WOW more fps.

Your performance improvements may vary, keep that in mind, having no fps at all doesn't mean you'll have fps now.

What are you waiting for? GET IT, it fixes shit and improves fps, no reason not to get it.

Sunday, June 11, 2017

Black Dragon Update 2.7.6: Interpolation and Position~ation?

Positionation? Really? Very bad attempt at making up words to rhyme.


So 2.7.6 adds mostly a lot of internal work, much of which you won't notice directly but you can now change the position of the pelvis bone and interpolate between positions, YAY!

You can now also set the interpolation method, either linear or spherical linear and its interpolation strength (NOT the time it takes, that entirely depends on the strength).

You can now also double click to load poses and the save button as well as name line editor has been moved to the pose tab... because it really belongs there.... load and delete are still in the other tab.

Soon.



You should now also be able to save without a folder (it should create it automatically).

I snuck in some extra changes too, brightened tone mapping a tiny bit, pitch black shouldn't be completely pitch black anymore and dark/black textures should now show their details again, even in shadowed/dark places. I will most likely finetune this a little bit more.

BTW, the shortcut for locking depth of field focus has been changed and should work properly now. Can't believe i've ignored this for so long even though it was pissing me off really hard every time i used it.

Remember. Start pose, then edit the sliders, otherwise no change and whatever you do, DO NOT ever stop all animations (via the window or menu) while having the pose animation running otherwise you'll end up breaking it and need to relog to fix it. I'll be fixing that in coming updates.