Forums » General
The Vultures have all been updated to use the new mesh, with slight tweaks to the spin constant to compensate for very small differences in turn rate handling.
A totally new "skin" of the Greyhound has also been released, the Camo Edition, available to Long Term Supporters only, and sold in Corvus space.
The Holiday Promo time is now in effect, as well. Have fun, everyone!
A totally new "skin" of the Greyhound has also been released, the Camo Edition, available to Long Term Supporters only, and sold in Corvus space.
The Holiday Promo time is now in effect, as well. Have fun, everyone!
That looks pretty cool! Thanks!
High priced "paint job" on the Hound - why not make some changes to specs to make it worth the extra 75k???
I hope this is not the only benefit offered to LTS
I hope this is not the only benefit offered to LTS
love how fast people are to whine at change, let's revert the game back to test :p
I find it hilarious this is called Camo Edition, so novel. I don't mind it.
Here's what it's supposed to look like, I think:
However, there is a problem with the Vulture. Someone I fought today was apparently missing the textures, for the Vulture and the Greyhound.
However, there is a problem with the Vulture. Someone I fought today was apparently missing the textures, for the Vulture and the Greyhound.
Idea, call the no texture glitch a Stealth Edition.
Crusader: No. Did you not pay attention to that other thread where we just got done saying things like that are bad?
I picked up a camo edition last night and it looked like the same old hound to me.
Graphics issue?
Graphics issue?
@tarenty: I should think that, if the ship is partially invisible to you, that YOU are the one missing the texture.
Regarding the cost: Aren't we always saying how rich we all are and that there should be some credit sinks ahead of an economy redux?
Regarding the cost: Aren't we always saying how rich we all are and that there should be some credit sinks ahead of an economy redux?
<sigh>. So, that was a really long release last night, and the shader was supposed to have been well-tested a month or two ago, when it was implemented. During the release last night it worked fine on Ray's NVIDIA laptop and my intel-integrated laptop, but ATI chips apparently have some sort of problem with it (compiles and loads fine, reports no errors, and then doesn't work).
I discovered it last night on my (ATI) desktop, and reported it to Ray, but I wasn't sure if it was specific to my game-installation or not (I have a lot of weird development crap in my install), and I was literally falling asleep.. so anyway, I didn't post about it at that time. Ray discerned that it's an ATI-specific issue today and is in the process of pushing a release to temporarily work around it.
vskye, what kind of device were you on last night? There is a graphics issue on Android (unrelated to the above ATI thing), which is also being fixed. But, if you were on a desktop, we'd love to know what kind of hardware.
I discovered it last night on my (ATI) desktop, and reported it to Ray, but I wasn't sure if it was specific to my game-installation or not (I have a lot of weird development crap in my install), and I was literally falling asleep.. so anyway, I didn't post about it at that time. Ray discerned that it's an ATI-specific issue today and is in the process of pushing a release to temporarily work around it.
vskye, what kind of device were you on last night? There is a graphics issue on Android (unrelated to the above ATI thing), which is also being fixed. But, if you were on a desktop, we'd love to know what kind of hardware.
Client update released. If anyone continues to have visual issues, let us know.
Fixed-Function chips will not see the new overlays (they just see the original texture, for instance without the "camo"), that is a known choice on our part. So that means anyone without modern "shaders", which can be Linux under certain conditions, or really old GPUs.
Fixed-Function chips will not see the new overlays (they just see the original texture, for instance without the "camo"), that is a known choice on our part. So that means anyone without modern "shaders", which can be Linux under certain conditions, or really old GPUs.
Inc. It was on a laptop, HD3000 Intel I-5 Sandybridge. Linux 64-bit client.
It might be related to this: http://www.vendetta-online.com/x/msgboard/6/28245
Ticket 2015.
It might be related to this: http://www.vendetta-online.com/x/msgboard/6/28245
Ticket 2015.
In other words, your bug fix for this:
Disabling shaders because of opengl driver bug for Intel 915/945 chipsets.
Disabling shaders because of lack of s3tc/dxtc support.
Effects anyone with ANY Sandybridge chip, but Ivybridge is fine. Horsecrap. (Linux specific)
Some type of switch to disable this in the config.ini would be nice.
Edit: And yes, I do have s3tc support, it's just your damn workaround borks it from working.
Disabling shaders because of opengl driver bug for Intel 915/945 chipsets.
Disabling shaders because of lack of s3tc/dxtc support.
Effects anyone with ANY Sandybridge chip, but Ivybridge is fine. Horsecrap. (Linux specific)
Some type of switch to disable this in the config.ini would be nice.
Edit: And yes, I do have s3tc support, it's just your damn workaround borks it from working.
The next client update is going to exclude Sandybridge from the workaround.
Awesome Ray! I'll send you some beer. I suppose you can share some with Inc if you want to. ;)
@tarenty: I should think that, if the ship is partially invisible to you, that YOU are the one missing the texture.
That screenshot was not taken by me, Whistler, as is evident by the fact that I cannot be 46m away from myself. It was also taken on an ATI machine, so that was likely the issue.
That screenshot was not taken by me, Whistler, as is evident by the fact that I cannot be 46m away from myself. It was also taken on an ATI machine, so that was likely the issue.
Changelog:
*** Vendetta 1.8.272.1
- Added Stealth Ships
*** Vendetta 1.8.272.1
- Added Stealth Ships
The next client update is going to exclude Sandybridge from the workaround.
Can we please please PLEASE have a config option to turn that off? Not everyone uses old broken buggy drivers... :(
Can we please please PLEASE have a config option to turn that off? Not everyone uses old broken buggy drivers... :(
Yes, that will be there as well.