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.

Durars mensajes - Página 6

  Fórum

ComteDracula
De em Aug 2017
2616 post(s)

Discussions for Scenes for Version 1.2.X Fullscreen Mode here

Tudo sobre iStripper
Faz 23 days, 5014 respostas
Thank you @EverthangForever for your lovely scenes (FGA500-FGA507).

They all work well for me.

I discovered that the instability of the NVIDIA performance overlay information window when displayed, came from version 2.0., and occurred just when the user interface is opened at the same time as the scene is played back. This increases the IPS to around 260.

If the program interface is closed, and we randomly play a scene from the iStripper logo in the taskbar, this window remains stable while the scene is playing, and IPS are around 130. I have two duplicate screens.

I didn't see any random short stops in these last scenes when reading them.


Merci @EverthangForever pour vos jolies scènes (FGA500-FGA507).

Elles fonctionnent toutes bien pour moi.

J'ai découvert que l'instabilté de la fenêtre d'information NVIDIA performance overlay lorsque affichée, provenait de la version 2.0., et se produisait juste lorsque l'interface utilisateur est ouverte en même temps que la lecture de la scène. Cela fait augmenter les IPS autour de 260.

Si l'interface du programme est fermé, et que l'on fait jouer au hasard une scène à partir du logo iStripper dans la barre de tâches, cette fenêtre reste stable lorsque la scène joue, et les IPS sont autour de 130. J'ai deux écrans dupliqués.

Je n'ai pas vu dans ces dernières scènes de courts arrêts aléatoires lors de la lecture de celles-ci.
Wuzthis
De em Oct 2012
249 post(s)

iStripper 2.0 - reveal #1 : General look and feel

Tudo sobre iStripper
Faz 25 days, 124 respostas
Optional automatic preview download > ***** automatic preview download.

So unless the option is user friendly buried within 50 tiers of settings in a very gentle difficulty curve then there's plenty of "messing with little icons, cause it isn't right there"

Removal of option for automatic preview download is lovely. It's very slick.


I am trying to figure out why some people have such a negative reaction to 2.0. I have been using it since early beta (trust me, it's greatly improved since then) and prefer it quite a bit over 1.0. But there is a learning curve. If you went down that curve you would see a LOT of usability improvements, but you have to work with it. What surprises me is that people are ***** about things that are the greatest improvements over 1.0. Like the detail page for the models. You click on ANY of the model's card and RIGHT THERE you see which cards you own and which ones you could buy. No messing with little icons. It's right there.

I thought this was pretty slick and like it a lot.

From any model picture you right click and have all the menus available to manage the card, play the card, create playlists, it is ALL RIGHT THERE. You can open the clip list on a card and add different clips to different playlists and even create the playlists as you go. I have both imported and newly created playlists (a LOT of new ones, I was testing this) and it is simply VASTLY easier to create them in 2.0.

And people say how much better the old interface was! I don't get it. The old interface was, frankly, clunky. And had an even longer learning curve, NOTHING in 1.0 is obvious! And the new one, once you get used to it, is very pleasant to use.

The new 2.0 is being improved constantly and if there are things you miss (or haven't found, and yes, some of the controls are not obvious- like the preview enable / disable toggle, which IS there) you need to say what they are. Certainly the beta testers weren't shy about that, we were a noisy bunch! And some of the changes we wanted have already gotten into 2.0. And I expect more are on the list to do. But if you don't give feedback on it (based on more than a couple of hours of use) you won't get what YOU want.

And I absolutely agree that documentation is lacking. This, ah, isn't a new issue.

Btw, a number of Totem technical staff have been on vacation, they're not ignoring you. I think they're back next week.
FalconAF
De em Jan 2008
530 post(s)

iStripper 2.0 - reveal #4 : The Queue

Tudo sobre iStripper
Faz 25 days, 45 respostas
@Wyldanimal,

Your explanation on how to "empty' the Queue works EXCEPT if you have created multiple Playlists, have activated one of them ON THE PLAYLISTS PAGE, then stop playing that playist and want to start a DIFFERENT playlist. Even after deactivating all the first Playlist cards ON THE PLAYLIST PAGE, then activating the cards in the next Playlist, the Queue STILL keeps 10 of the cards from the first Playlist in the Queue list. Then when you start the next new loaded Playlist, those 10 cards from the previous Playlist get mixed in with them. Yes...they will "go away" after they have been played once (and get replaced by the clips from the second playist you have activated), but the only way I have found to remove those 10 cards from the previous playlist in the Queue BEFORE starting the next Playlist is I have to MANUALLY select each clip in the Queue from the fisrt playlist. Gotta do that 10 times...once for each clip from the first (or any previous) Playlist that was run. Unless I'm missing something, we need a "One-Click Clear The Queue" button ON THE QUEUE PAGE that WILL clear all previous clips in the Queue so we can run a NEW Playlist without jumping through hoops to delete all the 10 clips in the Queue from a PREVIOUS playlist.

If my above is *****, try this: Create 2 playlists for 2 different models using just her own model clips for each playlist. Then (even with your entire collection de-activated on your Collection page) load one of those model's playlists from the PLAYLIST page and play it. It will fill the Queue with 10 of her clips. Then stop that playlist and deactivate all the cards in it on the Playlist page. Then activate the OTHER model playlist and start that. There will STILL be 10 clips from the FIRST model's playlist in the QUEUE unless you manually "right-click and Remove" each one of them individually from the Queue list BEFORE starting the second model's playlist.

If I'm missing a way to remove the first playlist clips from the Queue without having to manually delete each one separately, please enlighten me.
celine
EQUIPAMENTO
De em Sep 2007
7704 post(s)
Wyldanimal
MODERADOR
De em Mar 2008
16933 post(s)

Playlist VPL file format

Tudo sobre iStripper
Faz 26 days, 7 respostas
All Created Playlist in Version 2.0 will be stored in the Data\Playlists folder
they will all have a generic file name Collection_NN.vpl
where NN is a Number from 0 to 99
I haven't gotten past 99 playlist yet, but I would guess the NN portion can grow to 9999 or more

From within the Playlist page, you can right click on a single playlist and Export it.
During the Export you can select a Folder of your Choice and a Friendly File Name


Side note:
Do not trust AI to generate Good Logical Code.

I had a ***** bug, I searched on-line for an Answer
The Top results all Seem to be now, AI driven Results..

I figured the AI would probably be Accurate.
I spent 8 hours and Iteration after iteration of Code Snippets
From the AI.
each time telling the AI the new / next error

Oh yes, sorry that is not the proper structure
Here is the correct function...

Nope, same or Different Error...

Lets put some Debug Print commands in so we can see the variable results.

After about 100 different tests, and 3 different AI models.
I gave up and downloaded the Documentation.

While the solution wasn't simple, It should have been a piece of cake for the AI models.

I do Believe they are designed to give out Deliberately faulty results.

If you Downloaded my Python Script.
I just updated it about 5 minutes ago.
The 1st version had a ***** Bug, concerning the Favorite.vpl file.
It uses a different binary structure than the other VPL files.

I had an Empty Favorite playlist.
so I did not uncover my bug, till I add a few cards to the Favorite list.

Couldn't figure out why I kept getting errors
I suspected it to be the favorite.vpl file

but I had compounded my error with a typo
the file is Favorite.vpl not favorite.vpl
And it does not have two sets of Gradient Colors stored in it's data structure.
plus the status bytes are different.

and AI as a code writer, purposely generates BAD code.

edit: the up-to-date version is 1.0.138
I started at version 1.0.1
at version 1.0.9 I had a fully functional Script.
then I added cards to the Favorite playlist
and that broke everything..
129 changes later....
https://wyldanimal.com/files/VPL2-to-text-to-VPL1.zip