1031 replies to this topic

[randr]

Thanks to all the guys that put all the work into this latest 10.5 release. 

[wrd1972]

Wohoo. thanks devs. You guys seriously rock!!!

[jesperpark]

Awesome work everyone. Thanks to all the Devs that worked so tirelessly!!!

Now is everyone taking the summer off?

[bord]

10.5 is terrific. Thank you!

Moving forward is there any plan for a new graphic engine or do we have to wait until after 10.9? 3D lighting and reflections are my biggest wish list items as VP continues to improve, both for aesthetics and ease of building for authors. So much build time seems to go into prerendering graphics in other software.

[toxie]

There is currently a LOT of traction in the 3D rendering world, so at some point we will (have to) do a new engine i guess.. But it will be quite some work..

[Schlabber34]

Thanks for all the hard work you guys put into this! 10.5 is a huge leap over 10.4.

 

@toxie:

 

Any news about that ray trace renderer that you were mentioning a couple of months ago?

[Rawnei]

Thanks!

[fuzzel]

lol. Expect this in VP12

Thanks for all the hard work you guys put into this! 10.5 is a huge leap over 10.4.
 
@toxie:
 
Any news about that ray trace renderer that you were mentioning a couple of months ago?

[Schlabber34]

Yes, i know. Just wanted to know if this engine made a step forward or if 12 is still to early!

Gesendet von meinem SM-G955F mit Tapatalk

[toxie]

The future is ray tracing, that's for sure.. (but that comes from someone who does that professionally and drives it with passion since >10 years  )

 

The most tedious step will be to switch from DX9 to something newer (i.e. DX12 (https://devblogs.nvi...tx-ray-tracing/) or Vulkan) to make use of that in the future, and that requires a LOT more code, testing and performance fiddling, as one has to do much more stuff on ones own, where the DX9 driver/API helped with before with internal heuristics and optimized code. And that requires continuous work (i.e. lots of continuous spare time  :/).

 

Plus hardware has to become much faster to make it ready for tracing/sampling everything at good quality, otherwise one just has a blurry mess due to necessary noise filtering. So the visual benefits of ray tracing would vanish again (IMHO).

I hate filtering by heart, that's for example why the Ambient Occlusion in VPX is also almost not filtered, which makes it a bit more expensive but much better looking than what current games ship, even at high quality settings.

Edited by toxie, 30 July 2018 - 03:46 PM.

[Ben Logan]

Thank you Toxie and Fuzzel for countless hours of development. You guys are amazing.

[Drybonz]

I'm sure you guys don't remember this, but I mentioned some problems I was having with weird, white artifacts on my ball images.  It turns out it is related to the "overwrite ball image" option in the preferences.  

 

More discussion here:  https://www.vpforums...672#entry410856

[Pin-Pete]

Thanks for everyone in dev team for 10.5. Now waiting patiently for 10.6.

Edited by Pin-Pete, 01 August 2018 - 08:54 PM.

[jpsalas]

... Now waiting patiently for 10.6.

What? Isn't VPX 10.5 finished? I should like to wait for VP12

[toxie]

Hehe.. 10.6 first.. and then we have 10.7, 10.8, 10.9 still left..  

I'm sure you guys don't remember this, but I mentioned some problems I was having with weird, white artifacts on my ball images.  It turns out it is related to the "overwrite ball image" option in the preferences.  

 

More discussion here:  https://www.vpforums...672#entry410856

 

Okay, i'll have a look.. Thanks for pointing there..

[toxie]

@Fuzzel: Can you maybe have a look at this, too? It's driving me nuts at the moment to not find any clue at all, and i think you implemented the overwrite ball image code back then?

[fuzzel]

@Fuzzel: Can you maybe have a look at this, too? It's driving me nuts at the moment to not find any clue at all, and i think you implemented the overwrite ball image code back then?

Sure.

[Rawnei]

 

 

First things first,

@Rawnei AMD or NVIDIA?

Does your monitor/video card support this mode natively in portrait?  or are you making custom resolutions?

 

@toxie Does DX9 support screen resolutions in portrait in ~4K? do you know off hand?

 

 

Nvidia, native support, I have no custom resolutions.

 

res.jpg

 

 

Hey mates,

 

Late for 10.5 but maybe change it in 10.6.

 

I cloned the source to a local repo and found the fix and tested that it works, the order of portrait resolutions in the list is important.

 

VideoOptionsDialog Old:

         const int portrait_modes_width[num_portrait_modes] =  { 720, 720, 1024, 768, 800, 900, 900,1050,1050,1080,1200,1440,1600,2160,1440};
         const int portrait_modes_height[num_portrait_modes] = {1024,1280, 1280,1366,1280,1440,1600,1600,1680,1920,1920,2560,2560,3840,3440};

VideoOptionsDialog New:

         const int portrait_modes_width[num_portrait_modes] =  { 720, 720, 1024, 768, 800, 900, 900,1050,1050,1080,1200,1440,1440,1600,2160};
         const int portrait_modes_height[num_portrait_modes] = {1024,1280, 1280,1366,1280,1440,1600,1600,1680,1920,1920,2560,3440,2560,3840};

This will add 1440x3440 to options.

 

p.s. it's 2am I couldn't sleep so I didn't want to mess around with the sourceforge repo right now but I can contribute small stuff like this if wanted.

Edited by Rawnei, 02 August 2018 - 12:04 AM.

[toxie]

Thats very weird! I'll add your change, THANKS!

[DJRobX]

 

p.s. it's 2am I couldn't sleep so I didn't want to mess around with the sourceforge repo right now but I can contribute small stuff like this if wanted.

 

 

Toxie is super great about integrating changes.    He misses nothing.      It's probably easiest to publish your changes to your own public git or SVN repository.   Then it's easy for someone with write access to see and merge your changes into the official repo.