1353 replies to this topic

[fuzzel]

rev2781 is up:

 

- remove the old duration property and replace it with the function Duration with an additional parameter to define the final state after duration time expired
- add missing changes and collect changelog for/in commandreference.txt for 10.2 and 10.1
 

[jpsalas]

That did the trick with the lights

I tried this: light1.State = 2: Light1.Duration 3000, 1

The light1 was off, then after the command, it blinked for 3 seconds and then it turned on

[BorgDog]

Nice, thanks fuzzel.  I used up my likes for the day, but I like this

 

Works nicely for turning a light off for an interval as well, just have the blink pattern be 0, and the same lines as jp used and it will turn off for the duration then turn on, and I suppose if your blink pattern was simply a 1 you could do the same for a light that was off ie turn it on for a duration then turn it back off.

Edited by BorgDog, 09 September 2016 - 12:32 PM.

[BorgDog]

 

Is there a way for the script to read the VPx build version so it can check it and prompt user that a newer version is required to play?

Yes there are multiple functions defined for the table:

 

table1.version - returns a number VP_VERSION_MAJOR * 1000 + VP_VERSION_MINOR * 100 + VP_VERSION_REVISION

so for the 10.2 beta version table1.version returns 10200

 

table1.VersionMajor - returns the major number (10)

table1.VersionMinor - returns the minor number (2)

 

 

table.version works for me, but I get an error for VersionMajor, VersionMinor, and VersionRevision of "Object doesn't support the property or method:"

 

On latest revision 2781

 

revision was the one I was looking for so could pop up a message if less than 2781

[Shockman]

Nice, thanks fuzzel.  I used up my likes for the day, but I like this

 

Works nicely for turning a light off for an interval as well, just have the blink pattern be 0, and the same lines as jp used and it will turn off for the duration then turn on, and I suppose if your blink pattern was simply a 1 you could do the same for a light that was off ie turn it on for a duration then turn it back off.

 

You should not need to use your blink pattern up for that. Instead Light1.State=0: Light1.Duration=3000,1

 

Light1.State=1: Light1.Duration=3000,0  on then off.

Edited by Shockman, 09 September 2016 - 08:35 PM.

[toxie]

@BorgDog: Weird.. Fixed now..

 

EDIT: early in the morning, so: worked also before- it was just global and not via the table. whatever, i made it now so that one can use both (table and global) for all version variants.

Edited by toxie, 10 September 2016 - 06:38 AM.

[darkangel359]

Ok, so here is my problem.  I have used all versions of VPX from 10 to 10.2 beta newest revision from yesterday and when the tables start it's around 200+FPS but constantly drops.  After about 5-10 minutes it's all the way down to 10-15 FPS and is not playable at all.  Any ideas?  Also, when I quit to the editor it takes about 10-15 seconds before I can actually click or do anything on it.

Edited by darkangel359, 10 September 2016 - 03:33 PM.

[tttttwii]

Ok, so here is my problem.  I have used all versions of VPX from 10 to 10.2 beta newest revision from yesterday and when the tables start it's around 200+FPS but constantly drops.  After about 5-10 minutes it's all the way down to 10-15 FPS and is not playable at all.  Any ideas?  Also, when I quit to the editor it takes about 10-15 seconds before I can actually click or do anything on it.

I had the same issue. It was the operating system. I upgraded a 64 bit Win 7 to Win 10. I have tried almost everything to fix it, without success. A fresh win7 install fixed it for me.

[darkangel359]

Man, I was afraid of that.  I sure don't want to reinstall my O.S.  Anybody else have success running this in WIn. 10 64bit with no issues?

Edited by darkangel359, 10 September 2016 - 04:49 PM.

[Umpa]

Man, I was afraid of that.  I sure don't want to reinstall my O.S.  Anybody else have success running this in WIn. 10 64bit with no issues?

I run win 10 64bit. No problems! Not sure where to tell you to look. Make sure windows defender is disabled. I read people having issues with that

[freneticamnesic]

Hmm, why isn't there a Timer reference in the CommandReference.txt file? 

[darkangel359]

 

Man, I was afraid of that.  I sure don't want to reinstall my O.S.  Anybody else have success running this in WIn. 10 64bit with no issues?

I run win 10 64bit. No problems! Not sure where to tell you to look. Make sure windows defender is disabled. I read people having issues with that

 

Yeah, all antivirus software is disabled.

[Outhere]

running win 10 64bit. -  VP 10.1 --- No problems

[freneticamnesic]

TextBox also has no CommandReference.txt entries

Edited by freneticamnesic, 11 September 2016 - 01:22 AM.

[Shockman]

Also some could use some explanation. Many actually. One example, plunger filter. What on earth could clue someone in as to whether they want the plunger filtered or not? 

[darkangel359]

Ok, so fixed my problem.  After a little more time I decided to do what I do best which is hit the tech side of things.  Pulled up my performance monitor and see what was going on in the CPU & Memory areas while the game was running.  I noticed that the game was only utilizing one thread of 8 while running maxed at 100%.  I knew this wasn't correct so I manually set the affinity of the game to use all cores, after doing this it would work perfectly without any drop in FPS.  Of course I would manually have to do this every time I run the game (inconvenient) to say the least.  After further research I found the root cause to be that the game was set to run in compatibility mode for WIndows XP SP3, after disabling this everything worked.  So for anyone in the future having this issue check for this when using WIn. 10 64bit.  

[freneticamnesic]

TextBox also has no CommandReference.txt entries

yes it does why didn't I see it before

[fuzzel]

rev2786 is up:

 

- use middle mouse button to pan the editor view not alt+mouse move
- expose Version,VPBuildVersion,VersionMajor/Minor/Revision both globally and in table properties to avoid confusion
- fix versionmajor/minor/revision
 

Hmm, why isn't there a Timer reference in the CommandReference.txt file? 

Good question

[chepas]

Awesome cheers for the controls, any way to bump up the speed of the control a bit? Is a tad bit too slow.

[fuzzel]

Yes I can increase the speed a bit but you should move the mouse to fast as that would result in a strange hop and the whole table is moved outside of the editor view. I haven't found a good working situation for that.