can anyone give me a crash course on painting character clothing in unity

Many, the paragraph after the images is a bit too ambitious I think

> I want my game to be a mix of [list of AAA titles] but with [list of improvements and additional features]. How do I do that?

There should be a close reason for that.

@UriPopov you mean painting the textures for a cloth in Unity?

This may be off topic but not sure where to ask this...Why does .net throw a stackoverflow when you make too many objects that use more memory than the current applications stack? I thought non primatives were stored on the heap? Wouldn't it be heap overflow? always found this confusing...

@lambparade There are not many things off-topic here, specially when the chat is not very active :P

As for your question, I don't know. Haven't used .net in ages.

They probably store some reference to the heap object on the stack. At least that's what happens in C++.

@JoshPetrie I mean objects as non primitives. To my understanding objects are stored on the heap. The stack overflow exception was from a recursive function. I have it fixed now but I just found wanted to learn more.

@JoshPetrie So if I have an Object(Soda) and it has a name(string). That objects reference is on the heap and the string within the object is on the stack?

class

ohh i see now

my googling could not get me a clear answer

So if Soda references Beverage.id the id is on the heap right?

like i have a function to pull the name. getbeverageid(). and beverage is a class.

are you sure it's not recurisvely exploding and getting you a stack overflow

the revursive function was just bad and not needed. I was doing it as a learning experiment testing speeds of functions with and without recursion

I just mean that 77.45% of the time when you stack overflow, it's because you accidentally recursively looped

and not because you ran out of stack space

@lambparade take a look at the call stack when it throws

? all I see is (removed)

twas a failed attempt to type in a block of code I think

:43583169 Class Soda(){
string SodaId;
Beverage _beverage;
   public Soda(Beverage theBeverage)
   {
      SodaId = theBeverage.Id;
   }
}

Class Beverage(){
string ID {get;set;}

   public Beverage()
   {
   ID = "Coke";
   }

}

I'm trying to understand what things in this code are on the heap and what things on the stack in memory

if your function main is static void Main() { var b = new Beverage(), var s = new Soda(b); }, then there are 2 pointers on the stack

on the heap, there is one Soda instance that has a body 2 pointers large (ignoring the fact that all objects have a header that takes up some overhead), and one Beverage intance that has a body one pointer large. Often there'd be a string object on the stack but in your case it's a static string and is compiled into the intern table.

or "inline in the array" if it's an array of structs, which will be on the heap unless you stackalloc a fixed size array

So any properties within a class is always on the heap? So the ID properties in the Beverage class is on the head.

the entire class instance is on the heap

I think i finally get it now.

thanks for all the help guys

it was hard for me to google this because examples were confusing to me

@StephaneHockenhull uuuuuuuh niiice :D

sweet badduino demo dude

Now accepint tips on how to improve the snowfall particle system

smaller flakes

and perhaps more depth

for example, I think the effect at shadertoy.com/view/ltfGzn is pretty convincing

hmm

I so hate converting shadertoy shaders to unity