3889 replies to this topic

[fuzzel]

That is interesting. I have a R9 380 with latest drivers (not the beta ones) and all is fine. I have to test this on my cab which has an older AMD HD7770 though.

 

Anyway the next build will have a flag in the video options where you can force to use the NVIDIA API but only for NVIDIA cards. If it's not working on your AMD card you have to disable AO completely.

[hauntfreaks]

@hauntfreaks: what gfx do you have in your laptop?

 

its a i7 quadcore, 16gb ram

Intel HD Graphics 4000 v/card

 

worked fine until 2341

[fuzzel]

Strange, I tested it on a i5 with a 4000 onboard card without problems.

[hauntfreaks]

my drivers are from 2012 it says, I cant seem to find newer ones

[shadowshd]

Hi,

 

Rev 2341 is working fine on my cab :

 

- Asus B85M-E motherboard,

- Intel Core i7-4770,

- 8 Gb DDR 3,

- OCZ Agility 3 240 Gb SSD,

- MSI Twin Frozr 660 Ti - nVidia 358.50,

- Windows 10 x64.

 

++

[BorgDog]

Been getting that error (Fatal error: HRESULT 88760874 at RenderDevice.cpp:724) off and on this morning on my work computer, Rev 2341, Win7 Pro, x64, i5-3470, Intel HD 2500, yeah I know I really can't play on this but usually enough to do table layout adjust lights etc.

[hauntfreaks]

2331 working

 

2341 not working

[evilantal]

Also getting the fatal error on all tables...

 

Win7 Ultimate x64

AMD Phenom II X4

Nvidia GTX650 TI

[TedB]

this should hopefully not be necessary with the latest build due to an updated SciLexerVP.dll, but i'll check myself.

 

I have the dll issue as well, and being on XP 32bits I can't solve it by installing the C++ updates (can't install vcredist_x64.exe)

[toxie]

all these issues should be sorted out by our new bunch of fixes with the next build.

it will add some new settings to help with getting the old behavior back while optionally making the new features available for others.

[fuzzel]

Yes i can just second that. Just a small info about these crashes, for doing AO we need access to the depth buffer of DX but there is no official access to it in DX9. The only way to get the depth information is by using some well known but unofficial hacks . Depending on your gfx card and driver this hack works but as it seems it's not working for everyone. Nevertheless you need at least a gfx card which supports DX10.

[Shockman]

That's the first time I have read a z buffer of any DX needed a hack to access.

[Umpa]

Yes i can just second that. Just a small info about these crashes, for doing AO we need access to the depth buffer of DX but there is no official access to it in DX9. The only way to get the depth information is by using some well known but unofficial hacks . Depending on your gfx card and driver this hack works but as it seems it's not working for everyone. Nevertheless you need at least a gfx card which supports DX10.

So a requirement for vp 10 is a graphics card that supports dx10. Any other system requirements?

[fuzzel]

That's the first time I have read a z buffer of any DX needed a hack to access.

If you want to read it then yes that's not possible in DX9. Afaik this feature was introduced in DX10 or 11.

And no there are no other requirements so far.

[freneticamnesic]

Not a big deal but opening an older version of a table in the most recent build, make sure you re-enable the environment image - it cleared it on the two tables I've been working on.

[fuzzel]

rev2350 is up:

 

- adding switches to the video settings to disable ambient occlusion completely or only the dynamic AO

so if you had problems running VP with AO activated you can try to use newer drivers if possible or if nothing helps disable AO completely in the video settings.

 

- scintillaVP.dll fixed to work under WinXP again

 

@Fren: Don't get it do you mean an old table which was saved with an older version of VP doesn't show the env image in the editor in the new version of VP? That's ok because the older VP version didn't support an env image. Or do I miss here something?

[toxie]

additional info: if you have a NVIDIA based system and ambient occlusion or stereo 3D enabled, and it all of a sudden complains (whereas before it didn't), then you have to enable the 'Use NVIDIA API' in the video settings now.

[freneticamnesic]

rev2350 is up:

 

- adding switches to the video settings to disable ambient occlusion completely or only the dynamic AO

so if you had problems running VP with AO activated you can try to use newer drivers if possible or if nothing helps disable AO completely in the video settings.

 

- scintillaVP.dll fixed to work under WinXP again

 

@Fren: Don't get it do you mean an old table which was saved with an older version of VP doesn't show the env image in the editor in the new version of VP? That's ok because the older VP version didn't support an env image. Or do I miss here something?

 

older rev of VP10 that did support environment image... 

 

another "bug" - select an object in the editor then open material manager, rename a material but press "delete" while typing - it deletes the object from the editor, not the word in the material manager

sorry I should be using the bug tracker for these, crap

[fuzzel]

Ah ok. The deleting bug is already fixed

[toxie]

as for the env-image: cannot repro this, if i load for example CV or the default table, then the env image shows up as intended.