How to play at 320x200 in prboom+

[El Juancho]

I write the resolution on the cfg but the screen looks weird, its not 4:3, any advices?

[seed]

Then it means it doesn't scale properly.

 

Let me guess, it's stretched to fit the screen, isn't it? In this case, let the GPU perform the scaling, there is an option in your driver's control panel for this.

Edited December 21, 2020 by seed

[El Juancho]

2 minutes ago, seed said:

Then it means it doesn't scale properly.

  

Let me guess, it's stretched to fit the screen, isn't it?

Nope

[seed]

Ah, I see.

 

I've seen this before, but I'm not sure it can be fixed (someone correct me if I'm speaking nonsense). I seem to recall this is just how PrBoom looks like in that resolution. The actual game screen is bigger in it than in other ports, such as Chocolate.

[dmslr]

It might sound super dumb, but try 320x240.

[El Juancho]

24 minutes ago, dmslr said:

It might sound super dumb, but try 320x240.

It worked! But i still want to play at 320x200 :S

 

 

I know there is a way

Edited December 21, 2020 by JuanchoES

[dmslr]

It is 320x200 but stretched vertically 1.2x to match with "tall" pixels of DOS. I highly recommend to watch this video. It's really interesting.

 

Edited December 21, 2020 by dmslr

[maxmanium]

320x240 doesn't really work either -- the pixels don't scale properly and everything looks all fucked up. See: ammo numbers.

[El Juancho]

3 minutes ago, dmslr said:

It is 320x200 but stretched vertically 1.2x to match with "tall" pixels of DOS. I highly recommend to watch this video. It's really interesting.

 

Already watched that video, that youtube channel is so underrated

[dmslr]

6 minutes ago, maxmanium said:

320x240 doesn't really work either -- the pixels don't scale properly and everything looks all fucked up. See: ammo numbers.

Yep, the hud is messed up. But personally I could tolerate this rather than  W I D E  Doom.

Edited December 21, 2020 by dmslr

[El Juancho]

I just found this 

 

[Doomkid]

9 minutes ago, maxmanium said:

320x240 doesn't really work either -- the pixels don't scale properly and everything looks all fucked up. See: ammo numbers.

This is just aliasing, but yeah it's very annoying. I assume PrB+ has no sort of anti-aliasing features?

 

Also, 320x240 up to 640x480 are true vanilla resolutions, if that's what you're worried about. Just check Doom95 and see for yourself!

[Loud Silence]

Eternity Engine have same issue with 320x200 and 640x400. It looks like it does not stretch non-square pixels in those resolutions.

40 minutes ago, JuanchoES said:

I know there is a way

Chocolate Doom.

[El Juancho]

Sadly the doomworld post didnt fix the issue, im sad 

[El Juancho]

On 12/21/2020 at 5:09 PM, Loud Silence said:

Eternity Engine have same issue with 320x200 and 640x400. It looks like it does not stretch non-square pixels in those resolutions.

Chocolate Doom.

I dont like how the mouse feels in chocolate/crispy doom

[Redneckerz]

15 hours ago, JuanchoES said:

I dont like how the mouse feels in chocolate/crispy doom

Did you look at this specific post?

 

Can you describe the feeling you experience from Choco/Crispy? Choco should be the exact same as vanilla.

[El Juancho]

2 hours ago, Redneckerz said:

Did you look at this specific post?

Yes.

 

2 hours ago, Redneckerz said:

Can you describe the feeling you experience from Choco/Crispy? Choco should be the exact same as vanilla.

I don't know how to describe this problem in english but i just feel that the mouse in crispy/chocolate when you move very fast the mouse the sens feels wrong, like there is a max speed that the mouse can do, in prboom+ this doesnt happen, sorry if you dont understand, english is not my mother tonge

[Redneckerz]

17 minutes ago, JuanchoES said:

Yes.

So what did not work? At which step in that post did it go wrong?

17 minutes ago, JuanchoES said:

I don't know how to describe this problem in english but i just feel that the mouse in crispy/chocolate when you move very fast the mouse the sens feels wrong, like there is a max speed that the mouse can do, in prboom+ this doesnt happen, sorry if you dont understand, english is not my mother tonge

That sounds like a .cfg issue. Could you upload this .cfg or share a screenshot of the ingame mouse settings?

[fabian]

Maybe he should just disable mouse acceleration. 

[El Juancho]

1 hour ago, fabian said:

Maybe he should just disable mouse acceleration. 

already did

 

[El Juancho]

1 hour ago, Redneckerz said:

That sounds like a .cfg issue. Could you upload this .cfg or share a screenshot of the ingame mouse settings?

[fabian]

8 minutes ago, JuanchoES said:

already did

 

It's set to 1 in your screenshot. Seriously? 

[El Juancho]

29 minutes ago, fabian said:

It's set to 1 in your screenshot. Seriously? 

What do you mean ? I can't lower it more

Edited December 23, 2020 by JuanchoES

[fabian]

Oops, sorry, I was wrong. It's an acceleration factor that can't go lower than 1. My fault. 

Edited December 23, 2020 by fabian

[Diabolución]

Shur, does your monitor or TV support the 14:9 or 14:9 with zoom aspect ratios?

 

I cannot fucking stand this bug of PrBoom+ (only in software mode, and the only unaffected resolutions are 320x200 and 640x400), so I used to utilise 640x400 whilst setting the aspect ratio in the TV as 14:9 or zoomed 14:9, do not remember which one exactly, as a compromise solution.

[El Juancho]

7 minutes ago, Diabolución said:

Shur, does your monitor or TV support the 14:9 or 14:9 with zoom aspect ratios?

idk

[Redneckerz]

1 hour ago, JuanchoES said:

idk

You need to provide a bit more than idk. What is the monitor model? That kind of stuff.

[fabian]

On 12/23/2020 at 7:54 PM, Diabolución said:

 cannot fucking stand this bug of PrBoom+ (only in software mode, and the only unaffected resolutions are 320x200 and 640x400)

 

Any chance to test the little fix I posted to this issue a few days ago with your resolution? 

[Diabolución]

Thanks, @fabian!

 

I would appreciate that someone could apply that patch to the official version 2.5.1.4, and compile it without --disable-nonfree-graphics. I need, yes or yes, that version, which is perfect in my opinion save for that nasty bug.

 

[Never_Again]

@Diabolución, have you tried the workaround in prboom-plus.zip in the first post of the Github issue you referenced? Works with the original PrB+ and the UMAPINFO fork.