Age Verification
This website contains age-restricted material including nudity and explicit content. By entering, you confirm being at least 18 years old or the age of majority in the jurisdiction you are accessing the website from.
I am 18+ or older - Enter
I am under 18 - Exit
Our parental controls page explains how you can easily block access to this site.

Last posts - Page 343

  Forum

TheEmu
Joined in Jul 2012
7424 post(s)

iStripper mobile | Official version - Q&A

Everything about iStripper
November 18, 2022, 222 answers
@ComteDracula

Why don't you let the Totem team answer?

Because I am, like you, well aware that Totem provide little in the way of feedback - and, like any business, are very unlikely to explain basic business decisions. I, like you, would welcome more feedback. And also think it would indeed often be in Totem's interest to provide it - but not necessarily so in this case, where any explanation should be given to their investors not to their customers.

Customer satisfaction is not, and in my opinion never should be, the primary purpose of a normal business. If you look on customer satisfaction as a tool, or something to exploit, for increasing or maintaining profits then you will go a long way in understanding many business decisions. (and by profit I do not just mean short term profit).

Of course in reality it is not always black and white and many companies do indulge in things that are not purely profit driven - but as a first approximation it is useful to examine "offers" and other features by assuming that they are.

In the case of the mobile streaming service there will be a cost to the company in providing it. Possibly a considerable cost especially if you consider that streamed shows have to be served each time they are played rather than just once for a downloaded card. In order to justify (to their investors) providing the service that cost needs to be regained in some way, some possible ways are

    1 - Increased sales
    2 - Charging for it
    3 - Advertising

If increased sales would not cover the extra costs (something that the Beta version could have determined) then what do you think Totem should have done ?
EverthangForever
Joined in Oct 2009
4484 post(s)

Discussions for Scenes for Version 1.2.X Fullscreen Mode here

Everything about iStripper
November 18, 2022, 5111 answers
@Z22 yeah, and scale: -1, 1 to both da clipsprites, maybe
Great outcome to a question & answer guys...
works well this code , Thanks lots.
FG378A (not in the zip)
text: Info/infoFractalGarden738.txt
logo: Info/small_logoFractalgarden738.png
minVersion: 1.2.0.80
//uses Refract.fsh from Z22_SexualPredetor_V'1.1.scn by @ Z22
// amendments by @Z22
clip {
id: Clip
deny: top, table
nameGlowColor: 0.77, 0.70, 0.35
// allow: pole
}

clip {
id: Clip2
deny: top, table
nameGlowColor: 0.77, 0.70, 0.35
//allow: pole
}

texture {
id: BG2
source: Textures/Beige01.png
size: 3840, 2160
}

framebuffer {
id: BG
size: 3840, 2160
pos: 1920, 1080

sprite {
source: BG2
shader: fragment, Shaders/KilledByAPixel/GeodeMod01.fsh
}
}

framebuffer {
id: Girl01
size: 3840, 2160
pos: 820 , 980 //1520, 980

clipSprite {
pos: 0, 1080
standingHeight: 1800
sittingheight: 1500
source: Clip
scale: -1, 1
}
}

framebuffer {
id: Girl02
size: 3840, 2160
pos: 3000, 980 //2320, 980

clipSprite {
pos: 0, 1080
standingHeight: 1800
sittingheight: 1500
source: Clip2
scale: -1, 1
}
}

framebuffer {
size: 3840, 2160
pos: 1920, 1080
id: Refract

sprite {
source: Girl01, 0
source: BG, 1
uniform: t_offset, float, 0.0 // Original 0
uniform: t_factor, float, 1.0 // Original 1
shader: fragment, Shaders/z22/Refract.fsh
}
}

framebuffer {
size: 3840, 2160
pos: 1920, 1080
id: Refract2

sprite {
source: Girl02, 0
source: BG, 1
uniform: t_offset, float, 5.0 // Original 0
uniform: t_factor, float, 1.3 // Original 1
shader: fragment, Shaders/z22/Refract.fsh
}
}
////////////////////////////////////////////////////////////////////////////////
camera {
type: 2D
size: 3840, 2160
pos: 1920, 1080

sprite {
source: BG
}

sprite {
//pos: 0, 0 // pos has already been defined Girl01, these are offsets to the previous definition not absolutes.
source: Refract
}

sprite {
source: Refract2
}

clipNameSprite {
source: Clip
pos: -620, 680 // 2D
}

clipNameSprite {
source: Clip2
pos: 620, 680
}
}👍
Z22
Joined in Aug 2017
1776 post(s)

Discussions for Scenes for Version 1.2.X Fullscreen Mode here

Everything about iStripper
November 18, 2022, 5111 answers
text: Info/infoFractalGarden738.txt
logo: Info/small_logoFractalgarden738.png
minVersion: 1.2.0.80
//uses GetNormal3Oct.fsh from Z22_SexualPredetor.scn by @ Z22

clip
{
id: Clip
deny: top, table
nameGlowColor: 0.77, 0.70, 0.35
// allow: pole
}

clip
{
id: Clip2
deny: top, table
nameGlowColor: 0.77, 0.70, 0.35
//allow: pole
}

texture
{
id: BG2
source: Textures/Beige01.png
size: 3840, 2160
}


framebuffer
{
id: BG
size: 3840, 2160
pos: 1920, 1080

sprite
{
source: BG2
//shader: fragment, Shaders/KilledByAPixel/GeodeMod01.fsh
shader: fragment, Shaders/Calgon/Face3.fsh
}
}

////////////////////////////////////////////////////////////////////////////////
framebuffer
{
id: Girl01
size: 3840, 2160
// pos: 1920, 1080
pos: 1520, 980

clipSprite
{
pos: 0, 1080
standingHeight: 1800
sittingheight: 1500
source: Clip
}
}

framebuffer
{
id: Girl02
size: 3840, 2160
// pos: 1920, 1080
pos: 2320, 980

clipSprite
{
pos: 0, 1080
standingHeight: 1800
sittingheight: 1500
source: Clip2
}
}

////////////////////////////////////////////////////////////////////////////////



framebuffer
{
size: 3840, 2160
pos: 1920, 1080
id: Refract

sprite
{
source: Girl01, 0
source: BG, 1
uniform: t_offset, float, 0.0 // Original 0
uniform: t_factor, float, 1.0 // Original 1
shader: fragment, Shaders/z22/Refract.fsh
}
}

framebuffer
{
size: 3840, 2160
pos: 1920, 1080
id: Refract2

sprite
{
source: Girl02, 0
source: BG, 1
uniform: t_offset, float, 5.0 // Original 0
uniform: t_factor, float, 1.3 // Original 1
shader: fragment, Shaders/z22/Refract.fsh
}
}

////////////////////////////////////////////////////////////////////////////////
camera
{
type: 2D // Dont need 3D cam for what you are dong here.
size: 3840, 2160
pos: 1920, 1080
//pos: 0, 0, 2600 // z not required in 2D camera
//target: 0, 0, 0 //not required in 2D camera

sprite
{
source: BG
}

sprite
{
//pos: 0, 0 // pos has already been defined Girl01, these are offsets to the previous definition not absolutes.
source: Refract
}

sprite
{
//pos: 0, 0 // dito
source: Refract2
}

clipNameSprite {
source: Clip
pos: -620, 680 // 2D
//scale: 1.0, 1.0 // does nothing.
//rot: 0, 0, 0 //dito
}

clipNameSprite {
source: Clip2
pos: 620, 680
//scale: 1.0, 1.0
//rot: 0, 0, 0
}

}

works. but i couldnt see in face3.fsh where you flipped the Y so you just need to remove that
Calgon
Joined in May 2022
633 post(s)

Discussions for Scenes for Version 1.2.X Fullscreen Mode here

Everything about iStripper
November 18, 2022, 5111 answers
@Z22 @EverthangForever

Updated FG738 in the zip. ie: corrected left-right model orientationre-captioned & now uses only Refract.fsh & way less fb as per SPV1.1https://scenes.virtuastripper.net/ET_FractalGarden737-750.zip

Just tinkering around with that one with the new code and I found that if I offset the clip to the left, the refracted version has the wrong background. I tried offsetting the framebuffer to the same new position but that didn't fix it.


text: Info/infoFractalGarden738.txt
logo: Info/small_logoFractalgarden738.png
minVersion: 1.2.0.80
//uses Refract.fsh from Z22_SexualPredetor_V'1.1.scn by @ Z22

clip
{
id: Clip
deny: top
//allow: pole
}

texture
{
id: BG2
source: Textures/Beige01.png
size: 3840, 2160
}
framebuffer
{
id: BG
source: BG2
size: 3840, 2160
pos: 1920, 1080
shader: fragment, Shaders/KilledByAPixel/GeodeMod01.fsh
}

////////////////////////////////////////////////////////////////////////////////
framebuffer
{
id: Girl
size: 3840, 2160
pos: 1320, 1080

clipSprite
{
pos: 0, 1080
standingHeight: 1800
sittingheight: 1500
source: Clip
scale: -1, 1
}
}






////////////////////////////////////////////////////////////////////////////////



framebuffer
{
size: 3840, 2160
pos: 1320, 1080
id: Refract

sprite
{
source: Girl, 0
source: BG, 1
// source: Girl02, 2
// source: Girl03, 3
// shader: fragment, Shaders/z22/GetNormal3Oct.fsh
shader: fragment, Shaders/z22/Refract.fsh
}
}

////////////////////////////////////////////////////////////////////////////////
camera
{
type: 2D
size: 3840, 2160
pos: 1920, 1080

sprite
{
source: BG
}

sprite
{

source: Refract
}

}


redforleather
Joined in Jan 2009
172 post(s)

iStripper mobile | Official version - Q&A

Everything about iStripper
November 17, 2022, 222 answers
As with some other things (most notably for me the issue with the premium monthly/annual subscription), it is an understandable but also questionable business practice combined with just pretty bad and poor communication, by Totem generally but also some moderators of this forum, especially toward the probably most engaged customer base also writing in the forum.

First, I can generally understand the reasoning behind making the mobile site subscription based, and that this may attract a new and different customer base. However, when the subscription is essentially the price of purchasing three cards a month, I do wonder whether the same customers would not have been equally interested in buying three or more cards a month, when the site itself is generally attractive. Be that as it may, I don't have enough info to make a call here.

Second, though, it should be clear to Totem that this change to a subscription service is a disadvantage to many users who bought a lot of cards and saw the mobile site as a (long awaited) option to play them in this format as well. Instead, it is being sold as this exciting change, and this is just a bit insulting to the intelligence of the customers. The fact that I get, with having purchased over 5000 cards in total, 30 free days, which is basically like a free trial month, is just not that really exciting an offer, I am sorry.

Third, when some of the dissatisfaction and frustration is being voiced here, which is clearly the right forum to do so, instead of receiving any form of acknowledgment that this may not be such a great deal for everybody, but there were a number of things to take into account etc., there is very little of that (mostly silence on the official end) and instead you find moderators (!) who appear to find it necessary to basically berate customers for not having read the terms and services properly and that it was a BETA version all along etc. And that is just such poor communication, it is uncalled for, and again quite insulting (and again echoes the communication failure for the most part around the subscription issue).

I don't think Totem needs to be villified with what they did here, but it would be nice if they acknowledged that this is a mixed-bag at best for, let's say,a substantial number of customers, and that there would be a way and willingness to accept and respond to this criticism without reflexively defending Totem's business practices, even to the extent of being disrespectful to the customers (again, not everyone, but there are posts by some moderators where I don't see much moderating skill, for instance. but then again maybe it should be the team and not the moderators picking up the slack here).