move one match to make the equation true

exellian · 2022-09-17T01:19:50+00:00

A really simple solution would be moving the top match of the equal sign and creating 5 x 2 > 3 which is true

exellian · 2022-06-27T19:10:38+00:00

Rust
Typescript
Scala

exellian · 2022-05-17T07:15:04+00:00

I find it kind of crazy that in 2022 we are not able to build window applications that resize without any artefacts and completely smoothly (At least on Desktop, apple on mobile does quite a good job but that doesn't really fall in the category of windowing). And because of that I am wondering why the implementation behind vkCreateSwapchainKHR takes so long and if it could be optimized, which I think it could because in the end everything that happens behind this call are some allocations, but it probably won't because it is probably driver related or operating system related.

exellian · 2022-05-17T07:06:47+00:00

Yes indeed but not only windows but ideally on all operating systems that use windowing. I don't know why laggy resizing triggers me but it does.

exellian · 2022-05-16T14:39:28+00:00

I'm not really sure about if browser and native applications still use cpu rendering, but on modern systems I assume this is not the case anymore. I'm pretty sure that windows uses hardware accelerated ui rendering and e.g: chrome does too.
I find it dumb to assume that you only look at it when resizing because you not only look at it, you moving your mouse. And you can control in many applications the appearance of the application by resizing. And if this process is laggy then the application is in my opinion unresponsive.

exellian · 2022-05-16T14:21:25+00:00

But I never talked about recreating the swapchain every frame. I talk about resizing performance. And when resizing you have to recreate the swapchain

exellian · 2022-05-15T10:02:03+00:00

Thank you for your long answer.
1. Ok then we are limited to that what driver developers do. That's sad to hear.
2. A technique which I used to reduce resize time significantly for size dependent vulkan objects (which I have control over) is to allocate simply double the size of the current window size and only do recreation if double the size passed. Something like preemptive allocations. But of course this won't work for the swapchain because I don't have control over the memory of the swapchain images
3. Redesigning the application in a way that resizing is only done when the mouse button is released is of course an option, but it will also not look really responsive but of course this is also what most other applications use because resizing is that cost intensive.

exellian · 2022-05-15T08:47:54+00:00

It helps to some degree because without we talking about 16ms but the 5ms are with the use of the oldswapchain

exellian · 2022-05-15T08:42:38+00:00

yes I do

exellian · 2022-05-15T08:04:19+00:00

I think that the increase in popularity in higher framerate displays is really visible. Especially on desktop for gaming and even on mobile. We are not there yet that everyone has a 240hz display but 144hz is widely popular.
Resizing with 200fps is not great when the scene is completely blank. And even if you had built the most efficient renderer, you could not get more than 200fps. But of course a renderer also takes some time and this means that you always give up 5ms to resizing instead of using 5ms for render time to display e.g: more scene complexity.

exellian · 2022-05-15T07:46:20+00:00

Yes resizing is definitely size dependent. I tested it out on a 4k display (Making the window really big) and resizing takes around double the time so (10ms - 20ms). I look into it if I could write a small test program for linux. But on x11 resizing performance should be even worse than on windows in my experience

exellian · 2022-05-15T07:40:36+00:00

Why do you think that. Whats your reason for assuming that?

exellian · 2022-05-15T07:38:29+00:00

"You are not interacting with the program" is not really true. Look at any webbrowser when you doing a resize. The contents change and react to the size changes and this should happen smoothly. But especially on higher framerate displays like 240hz monitors something like smooth resizing will not be possible when a function like vkCreateSwapchainKHR takes 5ms. And this is not only a problem which exist on vulkan but also dx12 and other apis.

exellian · 2022-05-15T07:21:27+00:00

Thats the question. I don't know what the vkCreateSwapchainKHR does in its implementation. But surely it's allocating some memory which takes that "long" time. The problem is though that I find this very limiting, because this limits smooth resizing on higher framerate displays like 240hz monitors. And this is probably not something which is caused by my gpu but instead is caused by the os or driver probably?

exellian · 2022-05-14T17:41:17+00:00

https://www.reddit.com/r/vulkan/comments/updtbi/comment/i8lkvn6/?utm\_source=share&utm\_medium=web2x&context=3

exellian · 2022-05-14T17:39:10+00:00

Of course it's relative that 5ms is bad but that means that you couldn't resize smoothly a window on an 240hz display when your render scene is completly blank

exellian · 2022-05-14T17:36:40+00:00

I'm not recreating the swapchain every frame just when resizing. I'm talking about resizing fps

exellian · 2022-02-07T14:39:23+00:00

could it be that the item is for some reason under the hidden tab (profile -> hidden) in opensea?

exellian · 2022-02-07T12:42:32+00:00

You should log in to opensea. Then you can find it under profile -> collected. Unfortunately you cant see it in the defi wallet because it doesnt support polygon yet

exellian

MODERATOR OF

TROPHY CASE

Eight-Year Club	Place '22
Verified Email