KoboldCPP does not allow to set the generation resolution of 1536 to 1536

[ProfessionalMisunderstanding]

When I set this resolution, it resets it to 1280 by 1280. I am using the no cuda version of the KoboldCPP 1.17.3. I have an rx 6700 xt graphics card and I use vulcan render, what could be the reason? And I'm using an Illustrator-based model

[LostRuins]

Right now, the maximum resolution allowed is 1280x1280 (1.6 megapixel). This is because some models will crash when using a larger resolution. This may be changed in future.

[ProfessionalMisunderstanding]

Right now, the maximum resolution allowed is 1280x1280 (1.6 megapixel). This is because some models will crash when using a larger resolution. This may be changed in future.

I really hope that this will change as soon as possible, I read that Illustrator is trained specifically on 1536 x 1536 resolution, so I would like to set this resolution to get maximum quality. Thanks for the answer

[LostRuins]

You can still use larger sizes so long as the max resolution is kept. For example, you can use 1536x960

[ProfessionalMisunderstanding]

You can still use larger sizes so long as the max resolution is kept. For example, you can use 1536x960

Thanks for the advice, but I'm still losing some percentage in the detail of the picture, which I'm so afraid of, and the frames themselves turn out to be flat, like a movie frame, yes, it's cool if I wanted this result initially, but I need squares. So I keep hoping for a fix for this in updates, because without it, the advanced options come out useless. And by the way, when the engine changes the resolution of the image, it is indicated in the interface with the resolution that I specified during generation, and not which the engine set, I think this is a flaw

[ProfessionalMisunderstanding]

@LostRuins I want to try to raise the limits myself and then compile the application, purely for myself, but I can't figure out how to raise the allowed resolution, please tell me how. I found the function in sdtype_adapter.cpp

[wbruna]

@LostRuins I want to try to raise the limits myself and then compile the application, purely for myself, but I can't figure out how to raise the allowed resolution, please tell me how. I found the function in sdtype_adapter.cpp

Look for hard_megapixel_res_limit; bumping its value should be enough.

Alternatively, you could set both the debugmodeand sdclampedsoft options: the hard limit is doubled in this case (up to around 1800x1800).

[ProfessionalMisunderstanding]

@LostRuins I want to try to raise the limits myself and then compile the application, purely for myself, but I can't figure out how to raise the allowed resolution, please tell me how. I found the function in sdtype_adapter.cpp

Look for hard_megapixel_res_limit; bumping its value should be enough.

Alternatively, you could set both the debugmodeand sdclampedsoft options: the hard limit is doubled in this case (up to around 1800x1800).

Thanks, now I have problems with the Windows build, w64devkit does not create the koboldcpp.failsave.dll, koboldcpp_noavx2.dll

[ProfessionalMisunderstanding]

I deleted all the non-created dlls from the bat file, everything works, now I'm catching a buffer overflow - "requested buffer size (3397386240) exceeds device max_buffer_size limit (2147483648)" although 9.3 gigabytes out of 12 are occupied, I tried to remove vae on the cpu, I didn't wait for the end of generation, the processor wouldn't have survived it judging by according to the fan noise, 9.2 gigabytes out of 12 were occupied, I am sure that these 2 gigabytes could play into my hands. But I'm still very happy! Yes, the images are now generated for 4 minutes and 30 seconds longer, but the level of detail is incredible compared to 1024. Thanks for the help @wbruna , thanks for the programm @LostRuins , now it looks like I'll have to skip over versions to rebuild koboldcpp less often, but that's okay

[LostRuins]

You shouldn't need to rebuild from scratch as the options @wbruna suggested will work on a stock build.

I wonder if there's a better approach, how do we let users try large res while preventing bad actors from using it to crash random koboldcpp instances?

[LostRuins]

Okay I think what I'll do is simplify this a bit.
I'll increase the hard_megapixel_res_limit to 2048x2048 = 4 megapixels.
This is the "hardcoded" limit that cannot be exceeded by configs.
Then I'll make the default sdclampedsoft to default to 1024 if not specified (e.g. 0), which applies a soft limit of 1 megapixel.

So for noobs, everything works as it does now.
For experts, they can increase --sdclampedsoft at their own risk up to 2048.

@wbruna how does that sound?

edit: cb5755b

[wbruna]

@LostRuins , fine by me!

But the model-dependent hard_megapixel_res_limit behavior looks a bit strange (especially because it overrides sdclampedsoft by default for SD1.5). What about simplifying it further? (just as a suggestion, I'm fine with it as is):

• megapixel_res_limit = sd1.5 ? 832 : 1024;
• sdclampedsoft simply defaults to megapixel_res_limit
• if the user sets sdclampedsoft = 4096 with any model, let them enjoy the fireworks

The default protection would be there as before, and it'd be much easier to explain it to users: "you get this model-dependent safety limit by default; if you want to increase it, change sdclampedsoft at your own risk", with no third limit.

[ProfessionalMisunderstanding]

You shouldn't need to rebuild from scratch as the options @wbruna suggested will work on a stock build.

I wonder if there's a better approach, how do we let users try large res while preventing bad actors from using it to crash random koboldcpp instances?

Cool, thats mean I don't need to do it again. And it's easy, you just need to make this restriction only in the interface, otherwise the advanced options are useless, since the engine will limit the size anyway

[LostRuins]

Alright done 58ebff4

[wbruna]

Alright done 58ebff4

@LostRuins : LGTM, except the comments got out of sync. I can fix them in the next sd update.

[ProfessionalMisunderstanding]

Alright done 58ebff4

Thanks, now it will be much easier to get a high-quality picture!