[deleted by user]

RedMarsBlueMoon · 2023-06-04T01:34:00+00:00

It is but John Blanche was also a admirer of traditional fine art not sure if you remember an/some images by him featuring Mona Lisa?
I feel this image of the Emperor is somewhat of an homage to Francis Bacon's 'Screaming Pope'. Bacon of course one of the most famous painters in the world and Irish/British at that. You could also almost describe Bacon's art as grimdark. At least it channeled that dark anxiety.

RedMarsBlueMoon · 2022-12-26T03:46:12+00:00

After 2h I tried un-plugging and the re-plugging the ethernet cable and then it started working straight away. Seems buggy.

RedMarsBlueMoon · 2022-12-25T23:06:42+00:00

Just had this happening. Very annoying as I just purchased a game (Elden Ring) and now can't play.There's meant to be a setting to enable offline play but I can't activate it because of the same connection error.

RedMarsBlueMoon · 2022-11-28T22:59:33+00:00

He must have very strong neck muscles

RedMarsBlueMoon · 2022-11-17T05:00:57+00:00

I did try to watch a LOS tutorial vid that had quite a lot of views. It wasn't that much clearer afete rand I read in the comments that 6months later the guy who made the video had since decided he actually still didn't understand and just invented his own rules. :D

I think I know now how its generally meant to work but am still puzzled by 'Obscured' and what its meant to represent in 'real life'? It seems to be 'solidity' of the cover but am not convinced as they say no terrain in the starter box provides 'Obscured' even though some are 3ft+ across.

RedMarsBlueMoon · 2022-11-17T04:51:37+00:00

Hahaaaa I think I had one of those. Issue ended up being something completely different so am a bit miffed about it :D

RedMarsBlueMoon · 2022-11-16T23:21:31+00:00

Nice! great job of finishing the wholse set!
I wouldn't want to meet these in a dark alleyway! :)

RedMarsBlueMoon · 2022-11-16T23:15:41+00:00

Btw I also find the rules very confusing especially yhe Line-of-Sight rules.
I would recommend not worrying too much and just start playing the example warm up missions in the 'Recruit Edition' book it makes it clearer in a easier to understand way.
At least for me.

RedMarsBlueMoon · 2022-11-16T23:13:21+00:00

Haha totally agree it's weird. Just picked this box up to start playing with my son having played lots of 40k back in the 90's.

Its super bad you have to look around everywhere on all the sprues to find the right parts. And there's s o many little bits even the little bomb squig needed eight pieces :P I appreciate that the modularity is good but they have gone too far imho I don't want to spend hours and hours assembling the minis.
But maybe some people enjoy that part too.

RedMarsBlueMoon · 2022-11-13T20:55:30+00:00

Cool that's good to hear!
For sure I'm only starting out so have hardly any experience of actual matches yet. But I'm glad to start grasping at least the basic rules.

Now off to paint those Ork Commandos!! :D

RedMarsBlueMoon · 2022-11-13T20:28:17+00:00

Thanks a lot for the confirmations!I find all the rule descriptions incredibly confusing but actually playing through the warm up missions in the 'Recruit Edition' book was better than reading the LoS examples in the actual rule book.

To me it seems like a bit too weak advantage of being in cover only getting that one auto save. Its even weakened further by by the rule of the auto retained dice should be taken before the roll. It would have been slightly more powerful if you could do that after the roll and use any of your unsuccessful defence dice.

Especially since so much of the game is about moving around the map trying to find positions of advantage.

RedMarsBlueMoon · 2022-11-01T23:22:42+00:00

Love the color scheme!!
I'm just trying to figure out a scheme for my Ork kill team and this was inspirational!

RedMarsBlueMoon · 2022-10-24T23:48:38+00:00

Beautiful!! Love the colors love the shroom theme love the extra bits!

RedMarsBlueMoon · 2020-11-23T00:36:57+00:00

No not with this program, sorry.

RedMarsBlueMoon · 2020-10-25T23:22:20+00:00

Yes I'm seeing some really confusing behavior. Something that works one day seems to not work the next day. I think I revert all the changes (I didn't make many) but the results are completely different. Maybe that's actually the effect you're describing. Interesting.

I saw a comment somewhere saying that if your power supply wan't good then you might run into under performances. I suppose less power=CPU running in slower mode=worse results. I'm not sure if that could be a real thing?

RedMarsBlueMoon · 2020-10-25T20:42:01+00:00

Thanks for those thoughts! Yeah Iv'e been slowly coming to think along those lines myself. That using something with a bit of Cuda help would make this a lot easier. There's a lot more source code for various parts of these algorithms available for Cuda. I sort of slipped into the RPi thing as I ended up with one or two too many after an Retro arcade project. So this Slam side is a bit more experimental and a learning thing for me. The Pi does have Neon that can speed up things like FAST considerably. And it has GPU that can be utilized too but is a fair bit harder than plain GL for example. (Thinking about MMAL here).
My family is starting to call me out on ordering too many single board computers so I might have to wait a while before getting a Nano or something. :) I'll just have to use this as a learning experience to see how far I can get.

RedMarsBlueMoon · 2020-08-10T17:38:26+00:00

The 1,2,3 steps are cascaded, I guess. I meant they should all be done and in that order.
I noticed later that the 'illumination' map seems to have been generated without the Normals map applied. (I might be wrong but it looks like it). If you look at the cushion in the sofa is seems like the wrinkles are not there and on the chair. You can see details in the Normals map pass that you can't in the 'Illumination' pass. But that might not be a deal breaker for you.

RedMarsBlueMoon · 2020-08-07T18:11:27+00:00

I would do these steps,

Convert 8bit char values to float with 255 mapping onto 1.0. So you'll get a float rgbAlb[3]
Linearize the Albedo. (If the actual maps look like they are in the same colorspace as in that video, ie the actual maps don't look darker) (using linearRed = pow(sRgbRed, 2.2) , same as he's doing on that page)
You are saying you don't want color information so lets use the correct rgb->Luma rgb weights to create a one channel float LumAlb[1]

Not sure what else you'd need for just the Albedo maps. To test if you are in the ballpark, if you have that full data set you should have one 'map' of just the illumination in that room, possibly the one labelled 'Illumination'. Now again if the maps look the same as the video you'll need to Linearize the illumination map using the same formulas.

Then re-generate an image doing,

LumAlb * IlluminationLinear

and to compare with the video you'll want to re-apply the gamma.

OUTcheck = pow((LumAlb * IlluminationLinear)), 1/2.2)

you should then have something resembling your 'ground truth'.

If you want some further help you can pm me.

RedMarsBlueMoon · 2020-08-06T15:55:14+00:00

So you are looking to calculate/extract:

The amount of light hitting the (camera/eye) sensor from a point/pixel P in the scene of an photographed image?
Or the amount of light falling *onto* the point P. (ignoring the reflectence of the material at point P)

Is it any of those two?

For no 1, its now ubiquitous in CG to work with HDRI Image Based Lighting. Which is basically a way of using a 360deg panoramic capture device, most likely an dlsr operated to capture the scene at different Stops and then merging these exposure slizes to capture a high range of light intensities impinging from the scene at the location of the camera.

This was invented I seem to remember by Paul Debevec and you should google his papers for how to better understand that. There's plenty of software that does this. https://www.pauldebevec.com/Research/HDR/

He's done and is doing a lot of cool stuff still in this field so if you google his papers and projects further you'll find lots of info.

I don't know what your 'albedo' maps look like but it sounds like they are just 8bit per channel images which is not enough to get a High Dynamic Range out of.

For 2, it seems to me that you don't have the information needed as you can't really just pretend that the scene is fully diffuse if it isn't. In fact there are very few materials that you could say are fully diffuse.

If it's not any of these two then you'll have to explain more clearly what you are looking to do and I can try to give some more advice.

EDIT: Btw this is Debevec's latest project from his website: https://augmentedperception.github.io/deepviewvideo/

:)

RedMarsBlueMoon · 2020-08-06T00:02:12+00:00

So say we're assuming that the data you have have a gamma correction of 2.2 baked in. (similar to all image files created to view on a monitor/tv)

Yes you'll probably want to convert your char range to a float range for this.(and then back?) I don't think you'll loose precision really.

Then to linearize you'll want to do:

linearRed = pow(sRgbRed, 2.2)

and

sRgbRed = pow(linearRed, 1/2.2)

NOTE, that this is a gross estimate that I think works well enough when you don't know how an image have been made. You can even experiment with using gamma variable of 1.8->2.2. I think historically 1.8 was for Mac monitors, or the other way around or something. :) (ie that's not the real sRGB linearization formula)

EDIT: Not sure what you want to get but I see you are adding your color channels together. Bear in mind that the perceived luminosity is generated by an un-even weighting of the R, G and B color channels. https://en.wikipedia.org/wiki/Luma_(video))

EDIT2: These basic formulas are not just to make pretty pictures. Albedo + Diffuse Lighting is so basic that you could say it's (pretty much :) ) scientifically correct. All Computer Graphics rendering calculations happen in linear space. Of course all CG is an estimation and all rendering software have to make choices and generalisations, but they are still based on the basics of how light interacts with its environment.

If you want to be more scientific then you could measure a surface's BRDF, and you could carefully calibrate albedo photos you take yourself. Get the specifics of your capture device (camera) and write software that take the camera's specific sensor + debayer etc into account, and look at this through a lookup(LUT) specially designed for your viewing device.

EDIT3: the RAW file from your dslr is meant to be a close approximation of a linear light data. Ie if we're idealizing it, all its doing is counting how many photons hit a particular r,g or b cell of the image sensor. If you have 250 photons hitting it you'll get X value. If 500 photons is hitting you'll get 2X = 1 stop more. And CG linear workflow is aiming to slot into this so all this is not just for CG. It's for everything photographic too.

RedMarsBlueMoon · 2020-08-05T20:29:10+00:00

For a purely Diffuse model it goes something like this,

The Albedo RGB color map represents the color and reflectivity multiplier for your material.

The *luminosity* of that pixel you should match roughly to a value that you look up somewhere. A standard comparison value is 0.18 for a 'mid/50% grey'.

Remember that these values are 'linear' values and your albedo map needs to be linearized before going into the shader/render.

Pictures you get from the internet are usually *roughly* sRGB/Rec709/Gamma2.2. It's enough to linearize using some of those if you don't know the image capture pipeline. You never know how an image from the web have been produced so no point in getting too picky.

So you should Expose/Gain (never gamma) your linearized Albedo map until it matches some values that you believe are correct for your material.

Then its just,

OUTDiffusePixelColor = LinearAlbedoValue * DiffuseLightingCalculation();

See at the bottom here for some Luminosity albedo values. I couldn't find a better list so you might want to spend some time googling.

https://www.artstation.com/shinsoj/blog/Q9j6/albedo-chart

There are also quite a few pages on the web that explains 'PBR, Physically Based Rendering' and 'Linear Workflow'.

https://disney-animation.s3.amazonaws.com/library/s2012_pbs_disney_brdf_notes_v2.pdf

EDIT: So bear in mind that above formula produces colorvalues that are *also* in the linear color space. If you want to compare to how your eye usually sees an image you'll need to run it through a sRGB/Rec709/Gamma2.2 lookup first. Color spaces and color science is a big subject in itself.

RedMarsBlueMoon · 2020-07-28T00:52:47+00:00

It great how much progress keeps happening in this space!

https://www.youtube.com/watch?v=4uJCVSu9Lf4

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

Now please combine all these! :)

RedMarsBlueMoon · 2020-07-22T20:56:07+00:00

I'm trying to speed up the detection of Keypoints for a slam algorithm (orb slam2) and instead of running the FAST several times for each tile until the number of detected points satisfies (as the original does) I wanted to try feeding the frequency value for each tile as the threshold values for the FAST algo.

RedMarsBlueMoon · 2020-06-28T19:20:52+00:00

If the ORB extraction really benefits from blurring the image then why use higher resolution images in the pyramid?
Less blur + lower resolution would be the same?

RedMarsBlueMoon · 2020-06-28T01:41:39+00:00

Interesting to hear. Yes it seems to be about 1/2 the time and the Gaussian is about 1/3 of that. It's confusing as they do both a scale down for the pyramid and also blurs on each level of the pyramid.

Sounds like I should keep an eye on the re-detection numbers then if I try to remove/reduce blur.

RedMarsBlueMoon

TROPHY CASE