@All

Thanks for your input

I think @Z22's buffer sounds like the best route, sounds similar to this:
https://stackoverflow.com/questions/68931433/where-to-store-cached-data-for-access-within-vertex-shader

I could write something to automatically generate new scn files like @WA did to switch the shader and create any uniform needed to pass into the shader but I was trying to create a self contained solution that wouldn't need a helper program.

The approach of using a random texture works fine but I can't seem to get the syntax right when the texture is not the first texture.

I still don't understand what this code is doing:

uniform sampler2D texture0;
uniform sampler2D texture1;
varying vec4 gl_TexCoord[];
...
highp vec4 zero = texture2D(texture0,vTexCoord.xy); // input zero 0
highp vec4 one = texture2D(texture1, vTexCoord.xy); // input one 1

and what comes next to access a pixel of data from texture1 😠

Another, but complex, solution would be to use an external program to generate either the .scn file or a shader.

An external program could be written in any programming language you choose and could do anything you want making use of any inputs you think may be useful. It could take the form of a preprocessor for .scn files. But you would need to run the program before starting the scene which would be inconvenient and greatly limit the usefulness of this approach.

You could, however arrange to have the program run on a regular schedule e.g. to generate a new version of its output .scn file every few seconds. As the .scn and shader files are (I hope) read one when the scene is run any output from the external program would have no effect on a running scene but would affect its next run.

@Calgon

Use the static buffer hold the random number once created, the buffer can be one pixel but you cant use the alpha(its either 0 or 1) so you have >17 million values, you can doi a quick check to see if that pixel is uncoloured.

Give me a min an i will set it up for you

Yeah .. I found this card as well; I didn't see it labeled as 'special' but it is on the desktop version.

No real interest in the mobile site but if they add enough of the exclusive cards that I'm interested in seeing than I might subscribe for a month just to see what I've been missing.

I only looked for a minute to see if I could find it and didn't get sound but I will be going back to hear this voice!

Won't that change on every frame/pixel ?

Yes it will.

There is no easy solution available in iStripper other than one based on selecting a random texture from a folder of textures.

What is really needed for this sort of things is a "compute shader". The GLSL graphics pipe line comprises roughly the following series of "shader" stages executed in the following order

Initialise
Compute
Geometry
Vertex
Fragment

where each acts on the output of the previous stage and handles it in increasing detail.

The .scn file is handled at the Initialise and Compute stages (Animate clauses need actions after the initialise stage) providing data that is then used to compute the scene's geometry. The scene is then divided into a set of triangles each with three vertexes and each triangle divided into pixels each of which is handled as a fragment.

iStripper allows us to provide our own shaders for the vertex and fragment stages, but only allows us to provide limited data inputs to the compute and geometry stages.

It would be nice if iStripper provided more standard data via uniform variables - such as the date, time of day and mouse position etc. For example I have a set of clocks I would like to use as screen savers and it would be nice if they showed the correct time.

Another thing I would really like to see (but which I doubt will ever be implemented) is to be able to do simple calculations in the .scn file - with these calculations having access to such data as the date and time and to a few functions like sin(), cos() and rand().

ADDENDUM:

I suppose you could use one of Z22's feedback buffers to cache a calculation. A shader could be used to generate a copy of this "cache" for use next time or to generate its value if that old value was 0.0. But this would be far from a simple solution.

@Gator13

Go to your settings page, enable Advanced Settings, scroll down to the Clips section and set Preview Push to Never.

You should then probably go to the previews page and delete any that are appearing there.

I have always done this, and have never seen a preview except for short periods when I have deliberately enabled them.

Quick question, if I may: How do I stop previews from appearing all of a sudden? I mean, I'll have a card playing and all of a suddent the music stops and a preview starts up with a totally different person. Very annoying.

She really does have an inviting voice.

It is showing in the Latest Shows section. I even ran it... She really has a pretty voice.

Where does it say that?

@WA

here is an example random number function

Won't that change on every frame/pixel ? My objective was just to get one random number that is fixed until the scene is restarted.

here is an example random number function

// random number
uniform sampler2D tex;

float rand(vec4 co) {
return fract(sin(dot(co.xyzw ,vec4(12.9898,78.233, 45.8438, 100.0)*fract(iTime))) * (43758.5453*fract(itime)));
}

vec4 effect(vec4 color, Image tex, vec2 tc, vec2 sc) {
vec4 textureColor = texture2D(tex, tc);
float randomValue = rand(textureColor);
return vec4(randomValue, randomValue, randomValue, 1.0);
}
#endif

// In this version, the rand function takes a vec4 as input, and uses the x, y, z, and w components (red, green, blue, and alpha) to generate a random number.
//The dot product is taken with a vec4 that includes the alpha channel as well.
//
// This way, the resulting random number will be different for each unique combination of red, green, blue, and alpha values in the texture,
//which means that the randomness will be influenced by the alpha channel as well.

But since our textures are limited to being 8 bit
the real limit is 16,777,216 random start points.
(256 * 256 * 256 ) = 16,777,216

Yes @WA I understand that but I'm never going to need more than 100

Hi @WA

I've been trying that but I think I must have a screw loose somewhere.

When I try to access a pixel color to then generate a random number I have accessed the pixel with this:

vec4 myColor = texture(iChannel0, vec2 (0, 0));

but if I try to do the same on any other iChannel than the first one it doesn't work.

In @Everthang's combine2.fsh the syntax is like this:

uniform sampler2D texture0;
uniform sampler2D texture1;
varying vec4 gl_TexCoord[];
...
highp vec4 zero = texture2D(texture0,vTexCoord.xy); // input zero 0
highp vec4 one = texture2D(texture1, vTexCoord.xy); // input one 1

If I follow @Everthang's syntax, what would be the right way to access a single pixel color from texture1 ??

Having first set up 100 shades of grey that could be picked at random. I was very pleased with the result but of course this seems to have used up the one and only texture slot.

You created 100 single Pixel textures.
Then used a swizzle to get just the Taxture.r value from it.
so that is what Limited you to 100 possible Start points.

Knowing that the Texture.r is a 3 digit decimal value from 0.001 to 1.0 ( or 1000 posible values )
A larger texture of random colored pixels and a Combination of all of the color values
(Texture.r * Textuer.g * Texture.b)
gives a possible 1,000,000,000 start points

But since our textures are limited to being 8 bit
the real limit is 16,777,216 random start points.
(256 * 256 * 256 ) = 16,777,216

If your Texture also contained random level of opacity ( the Alpha channel )
then you can extend the number to 4,294,967,296 random Start points.
(Texture.r * Textuer.g * Texture.b * Texture.a)
(256 * 256 * 256 * 256 ) = 4,294,967,296


go back and re-read this post from @Theemu

https://www.istripper.com/forum/thread/27449/147?post=756851

In the scene file
you can pass up to 4 inputs which can be any combination of Textures, clips, or shaders
If you previously created a framebuffer using that shader.

source: ImageA, 0 // Assign ImageA as the first source (Channel 0)
source: ImageB, 1 // Assign ImageB as the second source (Channel 1)
source: ImageC 2 // Assign ImageB as the second source (Channel 2)
source: ImageD, 3 // Assign ImageB as the second source (Channel 3)
shader: fragment, TheShader.fsh

The Source Names are the ID name you use for your Texture, Clip, or Shader


Then in the Shader, you Use the Textures passed from the Scene

uniform sampler2D iChannel0;
uniform sampler2D iChannel1;
uniform sampler2D iChannel2;
uniform sampler2D iChannel3;

The Names iChannelN can be any Name you want to use for that particular input channel.

But it seems easy to just use the names as given in the Shader example to keep track of things.

Damn good incentive. If they repeat i will subscribe just for that and th VR.

I would go to another ATM that was free to use

Not always available, when you are out and about.

I can't wait. 👍 😎

I have just QA'd a new show by Candice Demellza - you will REALLY like this one when it arrives 😊

The Clemence card - interesting.

I wonder if this is an incentive to get the subscription?

😉

I noticed a Special Event Card on the mobile app. This is quite curious. Cheaper to get a mobile membership and not spend on the games of chance.

Hello tutti, de bien jolie carte ici

For me it was Jenny McClain, because I love big natural breasts. It was in july 2008 when I discovered VirtuagirlsHD.Full showShe was one of my firsts, too. But my first was this, also in 2008:I liked my second one better, though:

they have stayed with an upgrades are free policy even when remastering old cards

There have been forms of charging for 4K resolution, but remasterings of cards have always been free for people already owning the card. New prices have been charged on new buyers.
I personally appreciated this, and would like the policy to stay like so - would it be changed, I personally would not be willing to pay for upgraded versions of my old cards (am not going to pay for a card 2 times); and so, I would rather stay with the old versions.

There have been earlier posts in this thread, one of which you quote, telling you how to pass multiple texture to a shader. Namely using something like this in the .scn file

source: ImageA, 0 // Assign ImageA as the first source (Channel 0)
source: ImageB, 1 // Assign ImageB as the second source (Channel 1)
shader: fragment, TheShader.fsh

where ImageA and ImageB are the names used as the ids ifor two Texture nodes (or two frame buffers, or clips)

and in the .fsh file receive the two textures using something like

uniform sampler2D iChannel0;
uniform sampler2D iChannel1;

The names iChannel0 and iChannel1 can be replaced by anything you like.

Reboot the app - it should be fixed but it needs to clear the cache

For me it was Jenny McClain, because I love big natural breasts. It was in july 2008 when I discovered VirtuagirlsHD.Full show

She was one of my firsts, too. But my first was this, also in 2008:



I liked my second one better, though:

One random value to be used througout the run of the scene.

👍

@TheEmu - I know I'm probably being a *****. But this is not my original programming language and a lot of the concepts in it are new to me. In the past I've worked mainly in perl doing statistical things which are a lot simpler.

So what I'm trying to do is make interesting conversions of shaders and eventually my own. The one I'm working on at the moment is on Shadertoy here: https://www.shadertoy.com/view/cl23Wd

I've tweaked it so that each time you run it a random number based on iDate makes the shape of the cavern different:
Line 214 - 219

// Calgon - randomised start depending on time
float startSecs = iDate.w - iTime;
float randThing = sin(startSecs);

To bring that over to vghd I found we don't have iDate so I used 100 texture files to create a random number from the pixel shade.

...but this shader needs two textures as well.

So I'm really looking for a way to get 3 textures into the code OR 2 textures and a different method to create a random number that is constant "througout the run of the scene".

Once I understand how to do that, there are endless possibilities to tweak other shaders into novel designs that are different every time you run the scene.

Sorry to have to disagree with you as well @pickle1

BUT

After reading this post of yours

Quote Fixes are being put in place by the team. 😊and I can confirm it has now been fixed Unquote

I ran my istripper software as a test and got the same error with the Lara Lane card.

***** to disagree with you @Wyldanimal

BUT

Quote It's just like an ATM fee.
Pullout $20 it cost $4.00 in fees --> 20%
Pullout $400 it cost $4.00 in fees. --> 1% Unquote

Where I live if an ATM wanted to rip me off by charging me a fee to use it,
I would go to another ATM that was free to use

@Calgon

I am not sure what you mean by "How can I get it to just calculate the number once".

Do you want

One random value to be used througout the run of the scene.
A random value calculated separately for each frame with the same value used for each pixel
A random value calculated separately for each pixel with the same values used in each frame.

Some thoughts are

Use a vertex shader. Vertex shader outputs can be seen by subsequent fragment shaders as uniform variables.

Use a fragment shader to generate a tiny image in a framebuffer - the value of one (even the only) pixels in the image being the value you want to cache fr later use. Use the frame buffer as a source for a subsequent shader in a different node of the scene and extract the value you want from it.

You can use a variation of the second of these if you are already generating an intermediate image in a frame buffer as you can "sacrifice" a single pixel of this image to carry the information.


I also do not understand what you mean by

but of course this seems to have used up the one and only texture slot.

as you can have up to four textures acting as sources for a shader.

I'd pay all over again for some of my favourite "golden oldies".

So would I. It's funny that Totem does offer to upgrade some cards on a subscription basis. Although they've added all sorts of new revenue methods over the years, they have stayed with an upgrades are free policy even when remastering old cards had to have an additional cost.

I'd be happy to pay the full cost of a card for a remastered old card in 3K or 4K resolution. I'd be willing to pay, say half now and half when delivered for some cards with the promise of money be if the card isn't delivered in say 6 months.

If enough people subscribe, Totem goes ahead. Not enough and we get our credits back.

@TheEmu

2) Use the least significant bits of the elapsed time as your source of randomness. The variability of a scene's startup times and timing jitter when running stop this being predictable.

Tried to code that but it updates the random number throughout the time the shader is running. How can I get it to just calculate the number once, cache it, and be able to call it as needed ?

I'd pay all over again for some of my favourite "golden oldies".

@601bes Yep I think I would also. May be in time some do get the latest AI restoration treatment and perhaps it becomes a regular new feature for the App.

That show of Jewel is still a jewel.

highp vec4 zero = texture2D(texture0,vTexCoord.xy); // input zero 0
highp vec4 one = texture2D(texture1, vTexCoord.xy); // input one 1
... and further process that back into a format that a shadertoy shader would understand to be multiple textures that could then be used as normal.

highp is pointless for rgba 8 bit. highp is 16 bits per channel(i made this mistake ages ago). The output from the shader will always be in 8bit as we cant use even 10 or 12 bit hdr colour.


normal as in normal map? take a look at the lights and glass scenes, i create and use a normal map on the fly with them.

My Thoughts about using Crypto for Purchasing Credits.

Plan your Purchase to make the most of your Crypto.

Keep in mind that there is a cost associated to add funds to your Wallet to begin with.
Purchase enough funds to make that cost worthwhile.
$25 has about the same fee as does $200 dollars
So the cost is spread out better over the $200

It's just like an ATM fee.
Pullout $20 it cost $4.00 in fees --> 20%
Pullout $400 it cost $4.00 in fees. --> 1%

Check if there are ALT coins that you can use.
Altcoins usually go up and down more often then the Main Coin for that network

an Example is Sheba Inu
You might be able to buy Sheba when it's low
and then when it's value Goes Up, Buy your Credits.
Sheba can Swing 25% or more
Where as the Main coin might only swing 2 to 3%


You Gain in the Increased Value of the ALt Coin.

And that is what Crypto is about.
Buying low, and Selling or Using it for Purchasing when it's high.

Leverage your Gains.

I have everything all linked up as described in the how to posts and no NFT's. How long do they take or did I miss out?

@hobomonkey - Jon from Totem said the following on Discord;

Yes, you must have the latest version of the software that allows you to read trading cards.
You must have at least a bronze account with a transaction.
(this is a security to avoid people creating mass accounts to receive the trading card).

The sending of the trading card is not automatic.
We send the card every Monday to eligible people.
(we may send it again this week)

It is possible considering the late hour in Paris that you just missed the cut-off for it to be sent to you today

This transaction was simple and Straight forward.
Click the Buy button in iStrippers app
CoinGate asks what crypto you are going to use and generates an Invoice
Open your Wallet
Select the Coin to send
Copy the Amount directly from the coingate invoice
Copy the Address directly from the coingate invoice
( if your wallet has Pay by QR code, then just scan the QR code on th Coingate invoice )

Send the Payment -- > normally completes in less than 10 minutes.

Coingate will verify receipt of Payment, and your Credits are added to your iStripper Account.

I have everything all linked up as described in the how to posts and no NFT's. How long do they take or did I miss out?

I tested a buy of 250 credits with Crypto
Used my Coinbase wallet and Ethereum
$29.99 --> cost a total of $32.48 --> $2.49 in gas fees
I got the 20% bonus of 50 credits
so 300 credits for $32.48

$0.1082 per Credit. ---> 10.82 cents per credit.

Note:
When sending via coinbase
Make sure to select the correct network --> in my case it was the Ethereum network
Also, the QR code for payment wouldn't work for the web based Coinbase wallet.
( It probably works with the Coinbase App on your phone. )

When selecting the amount to send, Swap to eth, not $
you can copy the ETH amount from the Coingate pay invoice screen
Then Paste that amount of ETH into CoinBase.

Don't make the mistake of putting in $29.99 dollars, it is slightly more than that due to slippage.
You will end up short paying if you use $29.99 dollars.

Copy and Past the ETH
then copy and past the Address

You will get a confirmation screen from CoinBase with the fee to complete the transaction.
All paid from your coinbase wallet in ETH.
So Make sure you have enough ETH for both the cost of the credits and the Fee.

Thanks @ThEmu, I was hoping you would join the discussion

These all boil down to one of

1) Use a randomly selected image of some sort as your source of randomness

2) Use the least significant bits of the elapsed time as your source of randomness. The variability of a scene's startup times and timing jitter when running stop this being predictable.

In the digital clock scene I posted a few days ago http://bit.ly/3XL6O5P I already used 1) above. Having first set up 100 shades of grey that could be picked at random. I was very pleased with the result but of course this seems to have used up the one and only texture slot.

@Everthang mentioned that he uses framebuffers to get two separate textures into the shader e.g In FG842 so what I would like to understand how to do next... if possible is to convert that input which appears like this:

uniform sampler2D texture0;
uniform sampler2D texture1;
varying vec4 gl_TexCoord[];

...

highp vec4 zero = texture2D(texture0,vTexCoord.xy); // input zero 0
highp vec4 one = texture2D(texture1, vTexCoord.xy); // input one 1

... and further process that back into a format that a shadertoy shader would understand to be multiple textures that could then be used as normal.

Now, I can see the NFT cards on the carrousel (Paola Hard-Early Comer, Lana Lane-Shimmer Shot), with the price of a Triple Diamond Premium as I am and with the icon "Use my Gift card" and the icon "Buy in 1 click" to buy them. It seems that the NFT are managed like common cards by the software, but it doesn't work because I have no wallet. When I click on "Use my Gift card", an error is displayed saying "problem to connect with servers".

Fixes are being put in place by the team. 😊and I can confirm it has now been fixed

Year of the rabbit. 👍 😎

I just wanted to point out that, in the Lucky Rabbit game, the character 福 (fú) on the leftmost lantern in the background picture is vertically reflected, which is an incorrect representation of the character. However, 福 (fú) is often displayed upside-down to indicate that good luck has arrived. Happy Chinese New Year!

The ways I have seen for getting random numbers for use in shaders are

1) Use a texture that consists of random noise, use the elapsed time to select a point within that texture and then either use the value of the corresponding pixel or some function of it as a random number. At first sight you might think that this would create the same sequence of values each time but there is enough variation in the "start-up" time for a scene to overcome this predicability.

2) Just use a complex function of the least significant digits of a high multiple of the elapsed time. Or of the fractional part of such a function.

3) Use something based on a random selection of a texture from a folder full of textures and name this foder rather than a specific texture in a Texture: statement in the .scn file.

4) Instead of a random image use a randomly selected clip as the source of the texture used by the shader. This way you can expand the selection of random textures to include your whole iStripper collection.

These all boil down to one of

1) Use a randomly selected image of some sort as your source of randomness

2) Use the least significant bits of the elapsed time as your source of randomness. The variability of a scene's startup times and timing jitter when running stop this being predictable.

Or you can combine them.

Then use a function to amplify that randomness. For use in iStripper scenes you do not need a high grade random number generator.

If you want to generate a whole series of random numbers for a single output image then you can use the pixel co-ordinates as inputs to the "randomness amplifier".

So.... thought I'd use my Dolz from my newly set-up Coinbase wallet to buy some regular credits.... and bam !
If you plan to buy the NFTs then you might want to save your DOLZ for that. No point in paying fees to acquire DOLZ only to use it to buy credits that you can easily buy with a credit card.

You get 20% more credits so you dont have to wait for the reload bonus (if its still going to exist)

edit: 10% more credits,,, lame....

Now, I can see the NFT cards on the carrousel (Paola Hard-Early Comer, Lana Lane-Shimmer Shot), with the price of a Triple Diamond Premium as I am and with the icon "Use my Gift card" and the icon "Buy in 1 click" to buy them. It seems that the NFT are managed like common cards by the software, but it doesn't work because I have no wallet. When I click on "Use my Gift card", an error is displayed saying "problem to connect with servers".

@Calgon What are you trying to do? Are you inputing two textures and outputting one or do you want the same shader to do the operation on two textures and use both of them?

In the first case you can have 4 (think 4 is max) input textures that the shader can operate on and output a single texture. In the second case this is not possible on one sprite or framebuffer as they would both have the same id so you need two sprites with calls to the same shader.