@Z22 - I finaly ran your scenes with my NVIDIA GPU - they work when using that device.

I just made a quick and dirty change to the .scn file, for version 6. It almost made the scene work even when going back to the Intel GPU and the modified version works the same on both GPUs. I will have to leave soon so I do not have time to make properly thought out changes (though I know what I did wrong) but the experiment strongly suggests that the original version's framebuffers were just too big for the Intel GPU.

One observation - why do you feed the shaders with three copies of the same texture, why not just use one and change the shaders to use it three times?

Morgane Sexy Legs.

I always Like Melisa boobs. 😍

Morgane

Here is Kate Shoo one boob out.

Yes @stefnev1 pretty in pink Kate Shoo Sexy panties. Here the front.

YES always for me. 😛

I absolutely love your site...it is amazing...could you add some more info to the cards on top of your amazing collection:

1. Clip types...# of fully nude, nude, topless, non-nudity
2. Extra tags:
Panty pull, twerk, splits, acrobatic pole....I can provide you tags for the cards I have if you would like....

the walking dead got it going on.👍👍😎

@Z22 Superb outcome maestro ! Thanks lots for including great // comments.
Like @Emu says disregard the 'in' 'out', it relates more to vertex shader variables input use anyhow.
Ur vghd.log looks good 👍

Maya Mai /thread

Gotta love a woman that isn't afraid to rock a gorgeous bush.

Ahh, i see. I've not come across that before so not thought to use it.

It's quite possible i am overloading your gpu with the fb's that large(16k is taking the piss really) I suppose you can reduce everything down to 1080p or lower if you short on vram.. I think some intelGPU's have a limit of 2048x2048 come to think of it.

I am currently trying to figure out how to get rid of the black line around the girls. I don't think i can use a discard for 0.0 as a lot of the girls are wearing black so i thought i could use a blurred alpha/mask somehow. I really dont like the hard edge they have when it comes to the acid type scenes.

I get no errors logged when trying to use the newer versions - 4, 5 and 6 - but I still just see a blank background behind the performer. I do not see any obvious reason for this. One possible explanation is that the large framebuffers used in the scene are exceeding some limit of my system (if it is that then I guess it is the total texture memory size supported by the Intel GPU, but that is no more than a guess), however at the moment I am not in a position to investigate in any detail and it might be a few days before I can devote any time to it.

In any case, I am impressed by the effects seen earlier scenes that did work on my system, so, @Z22, keep up the good work.

@Z22

You asked which version I was looking at when I suggested not bothering with the in and out qualifiers. It was not one of you version but it was something in the last post in this thread by EverthangForever which included

in vec4 TexCoord;
out vec4 vTexCoord;
in vec4 FragColor;
out vec4 Colsize;

I have to admit though that I was a little ***** and thought it was something that you had posted, however the advice still stands.

I have just downloaded versions 5 and 6.

Yes, for example Emma Brown (iStripper cards). Also Alina in Racer and Home Alone.
Further Jennyi Gregg, Jenny Appach, Gina Devine Bikini Flowers), Christiana Cinn (Heated Affair - alas little nudity) and Ines.

My wish is that we will see more spontaneous discolike dancing on iStripper.

I thought the ink would be a problem for me when Kristy was first suggested.
I got over that real quick after buying her first card.
When I was young (eeek) there was an expression "I wouldn't kick her out of bed" and that certainly applies to Kristy. She could knock my door down any day... i can read 😈

Fixed a few more bugs and probobly created some new ones.
Added more comments.
Changes how i move the layers abit.

Acid Rain V6... The causer of headaches.

https://drive.google.com/open?id=0B52wt5m78EmUVFY1QlFqc0QzZ1k

Are their any cards where the models really get into dancing and just go for it?

I mean she's okay (not really my type)...I'm just waiting to get some more "Caramel" stuck between my teeth but you're probably sick of hearing that by now 😛

I agree with POPEYED. I find the shape of her body to be a little off putting. It's like she's really narrow from shoulders and breasts and then gets really wide at her hips. It's just a bit odd to look at or get use too. For me anyways.

Stella Cox pretty much stands still. She takes her clothes off, stands there, and fingers herself. I have her Sunny Spring Day card, and it'll be the only card of hers I will ever own.

If you're looking for a bit more entertainment as far as dancing, pole work, stripping, and slightly bigger breasts, I would recommend Viola. Especially her Meow card.

Foxy and Viola for sure.

I've been listening with a lot of Tom Petty lately due to his passing.

If the card doesn't show up at first in My Collection, go to the card you purchased and open it up to the card's details. Sometimes you need to do that for it to show up in collections.

@Z22

Unfortunately I don't think so.

Originally the only documentation for fullscreen scenes were the comments in the Totem Penthouse Multi-scene. Even now there is no official documentation but @Wyldanimal did creat a "tutorial" thread which explained many of the basics of creating scenes from just playing around with various values. Over time a number of people have added contributions to it.

http://www.istripper.com/forum/thread/27410/1?post=427679

With regard to swing or any other clips you can of course combine them into a scene with other clips and have a multi-model scene as per the screencaps.

If you go back to the very beginning of this thread you will also find some early scenes by various authors and some tips/discussions/etc. The reason that the shared screens thread was started was because some of the early shared scenes here were getting "lost" in the discussion so this was turned into a discussion only thread.

The exact reasons I do not know, but these are my explanations for it.

e0524
More effort for the special look. The outfit should match the cosplay character.

e0612 and e0618
Special scene files created for Helloween (e0618) and Christmas (e0612).

f0097
Card with four girls.

f0174
Unknown reason.

The Gloria card, it's her only XXX card, so I'm guessing that's why it's higher.

@Number6, As i suspected the swinging girls do look quite trippy. I take it we cant have the equivelent of

If Clip Type = swing
pos = 0, -2160
else pos = 0, 2160
endif

in the .scn file
So we don't have to have 2 versions of the same scene.

Which version are you looking at?

If it's V5 then I'm not sure which in/outs you are talking about. It should be taking in 3 copies of the same texture, those 3 copies are modified in 6 different (position and colour for each 3) ways and then combined into one output texture. Is that not what i am doing?

Other than that, what specific commands(and in which .fsh) are you refering to? You have to be a bit more basic for me to get what you are saying. :/

FOXY

👍

I will try the new version this evening.

@Z22

Don't bother with the in and out qualifiers for things declared at the start of fragment shaders. Fragment shaders can only have one output and this is the predefined variable gl_FragColor which, being predefined, does not need to be declared by you at all. Even if they could have other outputs there is absolutely nothing that could ever use these other outputs. Using "in" is redundant because it is the default and the only thing that can be a valid "out" is gl_FragColor. Things are different in vertex shaders, but we are only talking about fragment shaders here.

Everything else declared in a fragment shader but outside of its functions can only be either

1) inputs. which must be declared as either uniform or varying. Any input should have a value assigned to it by something that runs before the fragment shader otherwise it will just be zero.

2) Shader local variables which must not be declared as either uniform or varying. These will default to zero unless you assign them an initial value.

Note, every time that a fragment shader runs it gets a new set of these variables - if you give one a value it will NOT have that value in the next frame but will have been reinitialised.

If you try to import code from other sources please be aware that different systems will provide different sets of system specific uniform and varying global variables. You can rely on those begining with gl_ as those are specified by the GLSL language and must always be provided, everything else is system specific (such as the vUv variables that you have previously used). Within the iStripper system there are some of variables, such as u_Elapsed and u_WindowSize which are provided by Totem's code but if you are getting code from elsewhere that uses any uniform or varying variables other than the gl_ ones you will need to find out if iStripper provides any equivalents and if so what they are called.

@TheEmu

@Z22 seems to have solved it. Version 5 of Acid Rain does not appear to be producing any errors in the vghd.log and therefore I would have thought it should now run on your INTEL GPU.

My Windows 10 allows me to select a default GPU to use when starting any executable or to start a program using a particular GPU. These choices are offered as a pop up menu when you right click on an executable as shown in the attached image. To run iStripper with specific GPU I therefore

1) Stop it if it is already running - using the Quit menu option from the iStripper Systray icon because closing the GUI window does not stop the program, only its user interface. Very occassionaly it has not stopped properly and I have had to ***** it using the Task Manager, but that hasn't happened to me for a long time.

2) Find the iStripper executable and right click on it to bring up the context menu, then navigate through the menu until you find and use the particular items show in the attached image. Confusingly, if you don't know the history, the executable is called vghd.exe and is found on my system in the following folder

C:\Users\X-Format\AppData\Local\vghd\bin

and should be in a similar location on yours.

I do not have time to look any further into Z22's shader problem at the moment. Maybe I can do so this evening, but I can not promise anything.

@Z22

It also works with swings but initially it might be easier to do it as a separate scene.

Under the "Clip" declaration remove "top" from the "deny" line

Add new line

allow: top

In the framebuffer id: fb2, under "clipsprite" change the position to 0, -2160.

I can't see any errors in the vghd.log so it looks like this is OK.

PS
You could also combine the swing scene with the origiinal to give you both a swing and standing/pole in one scene. You will need to move the clip positions to the left and/or right to stop them clashing. Apologies if I'm teaching my grandma to suck eggs.

Yes, models like Tessa Fowler, Alice Brookes, Louisa Lockheart, Busty Alli, Beth Lily, Joey Fisher or Sensual Jane would be great. And I am totally in love with Estelle Taylor.

Cool, hopefully The Emu can run it too.

Looks Good @Z22

Runs fine on my AMD/ATI and no errors reported in the vghd.log

Right.. Fingers crossed..

https://drive.google.com/open?id=0B52wt5m78EmUSGtmRmgxcXg3Qms


Edit:- left one of the files out.. Corrected

nm.. fixed.

Question: How does anyone temporarily disable the NVidia GPU so that their rig resorts to intel GPU only as per @TheEmu's situation.? It stands to reason, if members cannot temporarily do that, surely they will never know whether anything is working to GLSL rules or not. Problems shouldn't be fractal but they seem to beget each other lol.

It depends on your set up. Many PCs now have the grahpics card built in and not necessarily INTEL. If you do not have a separate graphics card then you can only work with the onboard one. Usually you woulld have to go into the BIOS to enable/disable the onboard graphics if you have a separate graphics card. Many people would not have this option if they only have the one GPU. Mine is permanently disabled as my lowly AMD/ATI is far better then the the onboard graphics.

I suspect that @ThEmu has a laptop similar to my work laptop. It has dual graphics cards (mine is INTEL or AMD). It auto switches between the two dependent on the application. For high graphics usage e.g. AutoCAD in my case, it automatically uses the AMD.

I haven't looked at mine too closely (It is only used at work) but I am guessing there is a way to ***** it to use only one of the graphics processors. I have a feeling that @TheEmu did this a while back when there were some problems with some of the stuff he had done. Apparently it worked OK on one of his GPU's but other people were having problems. When he tried it on his other GPU it also exhibited problems. Now I think he tries everything on both GPU's just to be certain.

Yeh , have gotten rid of the problems TheEmu told me about(i think) but now i have another problem,

I can't find the correct way of modifying a textures colour so i get a bias to the right on the red channel/texture because its using the colour cycle as x position as well as for red. Why it can do that in the first place is odd, If i can sort out that problem i should be able to get it working as intended again.

c0 = vec4(-((fm0)*ColSize), rbgT, rbgT, 0.1);
//fm's come from a modulated sine function. rgbT and ColSize are ease of use constants

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// offset texture buffers(not currently offsetting)

blur0 = c0 + texture2D(texture0, vec2(vTexCoord.x, vTexCoord.y));
the line above is the problem. its inputing fm0 into vtexcord.x and using it as a colour...( .y too but to a much lesser extent.)

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// combine buffers
gl_FragColor = mix (blur0, blur1, blur2); // addition layers removed for ease of reading.

So i can see what it's doing wrong now i just don't know how to fix it. doh!

Hi @Number6 great..as you can imagine my tongue is hanging out a lot ;-)>

greetz @z22
I haven't a clue what I'm doing however...
I have been eliminating the 'varying' function
by applying the 'in' 'out' syntax elaborated in
https://gamedev.stackexchange.com/questions/29672/in-out-keywords-in-glsl
to RadialBlur2B.fsh
eg:
///////////////////////
//Original taked from "halloween" scene by totem(istripper)
//Adapted by z22
//tweeked to RadialBlur2Bxxx.fsh

uniform sampler2D texture0;
uniform sampler2D texture1;
uniform sampler2D texture2;

//varying vec4 gl_TexCoord[];
//varying vec4 gl_Color;
in vec4 TexCoord;
out vec4 vTexCoord;
in vec4 FragColor;
out vec4 Colsize;

//////////////////////etc.

I've done the eliminating of 'varying' also for a Combine3xxx.fsh and
ChromativAberation2xxx.fsh and it appears to work much the same as before.

This doesn't take into account all the issues @TheEmu cited about non compliance with
his intel GPU and not assigning a value to anything declared as a uniform.

Question: How does anyone temporarily disable the NVidia GPU so that their rig resorts to intel GPU only as per @TheEmu's situation.? It stands to reason, if members cannot temporarily do that, surely they will never know whether anything is working to GLSL rules or not. Problems shouldn't be fractal but they seem to beget each other lol.

@Z22

Have you looked in your vghd.log?

The scene appears to work for me as per your screencaps and it is a nice effect but it is throwing up dozens of lines of errors in the vghd.log. It even lists lines of shader code in the log and I've never seen it do that (although Totem may have added this feature).

Some of the errors are the ones that @TheEmu has pointed out. Some of the others may be a subset of this.

Unfortunately it is some time since I did any scenes and although many of them used tweaked shaders I really don't know enough about Open GSL to comment. In those days with the old VG interface it actually had a debugger that threw up the errors on the fullscreen interface (even for those that appeared to work). This no longer happens however the vghd.log does list Fullscreen (and skin) errors.

The problem is that unless you follow the actual standards of Open GSL there are always going to be graphics cards it will work with and those it won't. This is down to the graphics cards manufacturers and their interpretation of the standards - some will ignore the error and others won't.

If you look way back in this thread (or maybe the shared screens thread) there was one particular shader that worked fine on my AMD/ATI card but @EverthangForever couldn't get it working on his NVIDIA. I think @Wyldanimal solved that one at the time. It was just a single line that the AMD/ATI would accept but the NVIDIA wouldn't.

I'd listen to what @TheEmu is saying - he has a lot of experience working with shaders. Between you I am sure you can solve the problem. It would be greaT if you can get it working without the errors as it would look really nice with some of my old psychedelic scenes. Who knows I may even be inspired to get up off my fat arse and do some more.

PS - Hi @EverthangForever - how's it going?

Right, i think i know whats spazzing it out now.

I have a texture and i want to alter its colour but i have been adding the colour array to the coords array.

blur0 = c0 + texture2D(texture0, vec2(vTexCoord.x - (1*blurSize), vTexCoord.y - (-0.1*blurSize)))

Whats the correct syntax to do so?

Well, i have cleared out a lot of the crap and now all it does is posterize it... dafuk? It may just be an amplitude problem and a bit of tuning will fix it.

I there anyway we can open the scn.cache and make it readable so i can see what it did when it came across the problems?



The fm1,fm3,fm5 numbers were because i pulled it out of an old folder and i had forgot i had been using a input from a texture loacation(was messing with plazmas).

AcidRain4, like the previous AcidRains does not work on my Intel GPU, for exactly the same reasons as before.

Please note in a fragment shader you MUST not assign a value to anything declared as a uniform or a varying. On some systems it may work but it is still invalid to do so EVEN ON THOSE SYSTEMS and may stop working at any time, typically after a graphics driver update.

It is as if you had an algorithm that navigated the streets from point A to point B but its included a step that drove the wrong way down a one way street - it may work but it is not valid.

That said, even after I correct the declarations of the fm variables to be simple floats I still just get a blank background and I have no idea why.

I have found what the vUv variables do - they do absolutely nothing. The only place that they are used is to assign initial values to c0, c1 and c2, but these are then overwriiten by new values a few lines further on. Delete the delcarations of these variables, delete the lines that use them and add vec4 to the start of the lines that assign values to c0, c1 and c2. (The vUv vaiables appear to be left over from some old code that has been copied from somewhere that used a system that automatically provided these variables, the iStripper system does not, but as you are effectively not using them that is not a problem)

As I had rather too much wine at lunch I am not going to try to do any more study of why the scenes do not work on my system because I am likely to do more ***** than good)

Sure, & AcidRain4 and all your previous trials work fine on my NVidia 660ti ;-)
Only thing I changed was the allow
because Natalia ~the Punisher was made for this .scn lol ;)
@Number6 has a different GPU to NVidia I believe,
so it would be good to hear from that side as well.

I see. So i should post work in progress versions here and save the other thread for when they work as intended(that could take a while...lol).

Does the latest one AcidRain4 work on your system?

Yes.........appropriate lyrics Chicsans, but not Chilliwack methinks, ...........More Led Zep........but not to worry........:)

@z22 tks for your comments in the shader mods. Really helps lots 😊👍

You asked elsewhere why there are 3 threads for fullscreen stuff:
I'm not saying it is gospel or anything, however this is how i understand it:

Share thread was created before discussion began pushing too deep into the thread newly shared work links. It works best for more final bug-free or complete versions* of things that show something new or some new approach about scene presentation.

Fullscreen Discussion thread was created to take the discussion padding out of the shared thread so people can easier find newly posted or older shared download links in the afore mentioned* place.

The 'New Fullscreens available!' thread is part of Totem Team's own announcements of new features section. Like a news thread group. Its really intended for feedback on what changes they've recently done, rather than for posting members' own creations. Its easy to ***** this, because @TotemTeam rarely post as a newsworthy header there something special or new about fullscreen. I think the last mention was within the beta announcement that included new FS right arrow key use :)

@Mustang013

If you consider the girls pleasuring themselves either with their own fingers or with toys, XXX is hotter than full nudity. You will get bonus credits when you have 40 cards in your collection. You're almost there.