3889 replies to this topic

[freneticamnesic]

when not beta!

[toxie]

to cite 3DRealms: When its done..

[freneticamnesic]

I get some pretty sweet stutter in newest releases. I tried 2044 and it works fine.

[STAT]

Ok, Thanks Fren, toxie

 

3DRealms ? That was Blizzard

Edited by STAT, 28 June 2015 - 08:18 AM.

[gtxjoe]

Duke Nukem Forever! The game was 4 years late when they switched to "When it's done". It only took another 10 years to ship. To top it off the game was bad. I guess this is not looking good for VP10

https://en.m.wikiped...e_Nukem_Forever

[KieferSkunk]

Well, the more you all keep bugging the devs for a release, the longer it's going to take because of all the time they have to spend answering your posts, and/or the more likely they are to just give you the current buggy version as a final release.

Seriously, you folks are being really rude, especially since you're not paying fuzzel and toxie for their efforts.

[freneticamnesic]

lmao are you serious? no, no this is not rude.

[KieferSkunk]

lmao are you serious? no, no this is not rude.

 

Q: "Hi devs, is VP10 done yet?  When's VP10 gonna be out of beta?"

 

A: "We're still fixing some things.  No firm timeline set yet."

 

Q: "When's this free product gonna be done?"

 

A: "When it's done."

 

Q: "Seriously, release it already!  You guys are just as bad as Duke Nukem Forever!"

 

 

... and you don't think that's even just a little bit inconsiderate?

[freneticamnesic]

nope, because you're reading it as someone who doesn't know the people who are saying these things. As evidenced in the way you "quoted" them (that is, not verbatim, but as a loose interpretation of what was said to try and make your point).

let me explain further:

toxie said 

 

 

to cite 3DRealms: When its done..

 

which is clearly a reference to Duke Nukem Forever, which .... if you don't know the saga of that, read gtxjoe's link

 

to which gtxjoe replied

 

 

Duke Nukem Forever! The game was 4 years late when they switched to "When it's done". It only took another 10 years to ship. To top it off the game was bad. I guess this is not looking good for VP10

 

I don't know how you're reading that incorrectly, when the Duke Nukem Forever reference was brought up by the dev you're trying to defend.............. 

[gtxjoe]

Gotta love internet forums.  At least this is not Pinside     Yes, another bad joke

 

toxie makes 3D Realms reference = GOOD

gtxjoe makes 3D Realms reference = BAD

 

 

 

[freneticamnesic]

that'll learn ye, gtxjoe

[hauntfreaks]

 

Edited by hauntfreaks, 29 June 2015 - 03:19 AM.

[fuzzel]

You wanna dance? Shake it baby!

[KieferSkunk]

Fine, whatever.  Obviously, I'm not in the "in" crowd here, so I wouldn't know that you all are just having fun and the devs are just fine with that.

 

Guess you'll have to excuse me for being a little sensitive when I've seen those exact kinds of conversations rip entire communities apart in the past.  Forgive me for speaking up about something that, frankly, really irks me.

 

Yeesh.

 

 

Just to explain my side of this: Admittedly, I only know of fuzzel and toxie being on the VP dev team, but that's only because I've talked to toxie about core.vbs updates and seen fuzzel doing the releases.  I don't know who else is actually working on it, so I probably jumped to conclusions that the rest of you are all in the "consumer" category with respect to VP.

 

I've been seeing a lot of people pestering them about "When are we going to have a release?", to which fuzzel has consistently said something to the effect of "There's still more to do", "We're probably pretty close," or "It'll be done when it's done".  I thought I picked up on a small shred of growing annoyance with the questions.  In my experience, "When it's done" usually means "Please stop asking", and reportedly that's what the DNF devs were saying to the people who kept pestering them.

 

(And yes, I'm well aware of that "saga" - I know a person who worked on that project and I know that it was no picnic for him - especially considering what a crap game it turned into long after he was off the team.)

 

So again, you'll have to excuse me.  Touched a nerve.

Edited by KieferSkunk, 29 June 2015 - 05:09 AM.

[hmueck]

Actually, ... Stat asked about a VP10 download section, not the end of Beta...
So this was more a question to Noah than the VP10 devs...

[KieferSkunk]

Actually, ... Stat asked about a VP10 download section, not the end of Beta...
So this was more a question to Noah than the VP10 devs...

 

In the last few weeks, there've been at least three other people who have directly asked for a "final release" version of VP, or have commented that the lack of a final release was holding up table development (to which I replied that it shouldn't).  That's what I was referring to.

 

I totally agree that a download section for VP10 tables would be very nice.  Kinda sucks having to scour the forums for tables to test VP10 with.

[freneticamnesic]

It's not the same people asking so it's not a problem. We're all aware of all the nuances of forums - not just VPF -, no one is going to read 120 pages of a thread unless they read the first post on the first day. So when people ask the same things over and over, you just sign and reply the same as you always do, there's nothing you can do! You could put the information in the first post but...if they didn't read the rest of the thread why would they read the first one?

[goesta]

I think The Loafer does a great job updating all the download links for the test tables (Test Tables) !!!

Works for me ;-)

VP10 table testing - available right here!

[toxie]

guys, everythings cool.. no need for flamewars..

we wanna get this thing finished ourselves..

I get some pretty sweet stutter in newest releases. I tried 2044 and it works fine.

 

which table? and do you have an exact revision range? or is 2044 the exact last one that does not stutter?

[fuzzel]

rev2092 is up:

 

- calculate real height for every control point on the fly

- further optimize ramps draws/save memory and fix off by one error from last optimization
 

Regarding the ramp control points:

  in the editor: control points of ramps have a new read-only "Real Height" information. The "Height Offset" is just an offset for the current height.
  E.g.: Top/Bottom height of the ramp is 100. If you add 25 to the "Height Offset" the "Real Height" shows 125. This is more important if you use a sloped
  ramp with bottom height 0 and top height 60 and add new control points on the ramp. The height information is interpolated from one control point to the
  next one, so the "Real Height" shows you this value and the "Height Offset" can be used to easily adjust the height.