Formatting bugs

Started by deft [979003] on 30 May 2020 in Bugs & Issues.

38 replies · 720 views · thread synced 23 Sep 2026 · 4 days ago · View on torn.com

About this thread

Posts archived: 39 / 39 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts: 39
Discussion span: 30 May 2020 → 5 Mar 2026
Authority score: 62 / 100
Historical score: 67 / 100
Story score: 64 / 100
Engagement score: 72 / 100

People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.

Most-liked replies

deft [979003] · 3 likes · 3 Jun 2020
I think I've been thorough but it's possible I've missed something. The following list is on Chrome with 90% zoom and not working correctly: City https://www.torn.com/city.php#quick-links -- https://gyazo.com/e16547e21a5b8941fe427f3f05320b2d https://www.torn.com/travelagency.php -- https://gyazo.com/bf01c36c26b41ca2a3de0b3cd0ae2f96 https://www.torn.com/shops.php?step=nikeh -- https://gyazo.com/a458550edc4ef4a94329c3ba208f91cf https://www.torn.com/shops.php?step=pawnshop -- these all have same …
svyat770 [2114355] Tester · 2 likes · 14 Jun 2020
Hi there! Sorry for a quite long delay with the response. We successfully investigate the issue here. It seems to occur since Chrome v.83 and above. The rest of the browsers (like FF) in the latest version got the same …
svyat770 [2114355] Tester · 2 likes · 1 Jul 2020
We're on it right now. Just give us some time to figure out how to make things properly. Thanks.

deft [979003] 30 May 2020, 15:20 TCT · #1 · edited

Hello, I started getting formatting bugs on Chrome either immediately after or shortly after the event log update and it hasn't gone away despite clearing cache several times. It seems to be injecting an extra blank white cell into top rows of item which kicks the last item that is supposed to be there into an additional bottom row. I use doctorn and ublock origin as only scripts. I've disabled doctorn and it doesn't make a difference. What does make a difference is toggling the zoom back to 100% from 80-90%. I always play zoomed out because 100% is too close to fit so many items on a single page especially when I'm forced into adaptive mode when trying to downsize the browser and still forced to have it be 2/3 of my screen. I think this should be fixed as I can't be the only one playing from 80-90% on a regular basis. See screenshots.

https://gyazo.com/97a969f709e201242d7e4742bf9bb194
https://gyazo.com/3c15ad506fa34a8f419f63da67866b92
https://gyazo.com/5502846dc95a31eab6961a7890854f0e
https://gyazo.com/d827be74a3f1d819cb732426bb3db809
https://gyazo.com/9b802615da05ead2f8f87463c2c8a475

CloudJumper [1636201]Staff 30 May 2020, 16:02 TCT · #2

This is the third report that we have received on the same topic within a week. This was the original report and this was the other one on the same topic.

I will refer this to Joe to get an official word on the matter. Thanks..!!

Mentions: Forums Broken when not in 100% View · Forums spazzing out

Chedburn [1] Admin Developer 30 May 2020, 20:14 TCT · #3

I'm really not sure what to suggest. All examples work fine for me at different zoom levels.

I cans perhaps ask Sviat if he has any ideas.

Proxima [1879587] Wiki Editor 30 May 2020, 20:29 TCT · #4

Thanks deft. Knew I wasn’t alone with this.

Chedburn [1] Admin Developer 30 May 2020, 20:31 TCT · #5

Also this report.

Mentions: nonresponsive UI below 100% zoom

Rum4nyby [1567187] 30 May 2020, 22:26 TCT · #6

Don't forget my original report! This

Idk what happened in the past week, but it's been super annoying to play torn on 100%. Especially for me, when I split tabs on the same screen, the page layout is horrible on 100% zoom. Please do look into this, playing on 90% was seriously so much better, and there was no reason for it to stop working so suddenly last week.

Mentions: Forums spazzing out

Adrenalinas [1974447] 31 May 2020, 07:12 TCT · #7

same shit (if zoom out of 100% this shit happens)
Using chrome
It f**king annoying because I usually play on 80-90% zoom

90%/80%
[image: i.imgur.com]
100%
[image: i.imgur.com]

svyat770 [2114355] Tester 1 Jun 2020, 07:15 TCT · #8 · edited

Hi there!

Well, I would say generally you should avoid playing Torn in any resolution different from 100% zoom. It's even not about Torn, it's about how any web-page in any browser works. So if you change zoom manually you can get some weird layout for sure. There are no guarantees of how it will appear because viewport of the browser became like a custom one. It's not the way how it should go.

Of course, this is up to you to choose the mode to play. Just remember that we can do nothing in that case.

Thanks.

svyat770 [2114355] Tester 1 Jun 2020, 07:22 TCT · #9

By the way, I've double-checked the layout on less than 100% zoom (60% - 90%) on Chrome latest + macOS latest. All seems good on my side though.

Can you reproduce this issue in any other browser/OS and did you tried "Incognito Mode"?

Thanks.

Asshole [949262] 1 Jun 2020, 09:11 TCT · #10

The layout issues are there in incognito mode and Firefox browser too.

What is your desktop display resolution?

I have the issues in 1366x768 resolution.

Asshole [949262] 1 Jun 2020, 09:15 TCT · #11

I can understand weird layouts at something like 60% or 150% zoom but layout should be stable for atleast 90% zoom. There is absolutely something you can do to make it stable for 80-90% zoom in a browser.

svyat770 [2114355] Tester 1 Jun 2020, 09:26 TCT · #12

Can someone tell me is it happen on Mac or Windows?

Rum4nyby [1567187] 1 Jun 2020, 12:43 TCT · #13

Happened to me on windows, google chrome, latest versions of both

CloudJumper [1636201]Staff 1 Jun 2020, 12:51 TCT · #14

I can replicate the issue on my laptop running Windows and Chrome browser (Display resolution set to maximum available 1366 x 768). The issue doesn't exist on the monitor that I have connected to my laptop (Resolution 1920 x 1080).

deft [979003] 1 Jun 2020, 14:27 TCT · #15 · edited

Every other website I go to works well at 80/90%, only torn has issues now following the recent history patch.

Incognito on chrome makes no difference. Firefox it still persists in some areas while in others it's fixed. I have reproduced the same 5 screenshots from original post except they are on firefox instead of chrome. Companies and stock page is still broken format. Items and armory list you can see a weird effect at the top right but it hasn't pushed it into a lower row. Trades looks normal, and forums look normal, whereas on Chrome they bugged there. I should note both sets of screenshots are from 90%.

https://gyazo.com/f95de299eaada48d2587e1052962ad82
https://gyazo.com/5ddaa020d3b717740eeb8820a6474e0d
https://gyazo.com/3c15ad506fa34a8f419f63da67866b92
https://gyazo.com/19975ea0a806ee9a95b048efa31eac63
https://gyazo.com/adf03d631912c0cacc105972b3fa0c25

I'm on windows with 1920 @ 144hz, here's from dxdiag: https://pastebin.com/k1cfT0w2

------------------
System Information
------------------
Time of this report: 5/31/2020, 19:36:41
Machine name: DESKTOP-5LOCCFQ
Machine Id: {948D0FD0-86D0-4EE2-87FA-B4FA6D732240}
Operating System: Windows 10 Home 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: G1.Sniper Z97
BIOS: BIOS Date: 05/30/14 12:45:07 Ver: 04.06.05 (type: BIOS)
Processor: Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz (4 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16246MB RAM
Page File: 8950MB used, 9727MB available
Windows Dir: C:WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: Unknown
DxDiag Version: 10.00.18362.0387 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: The file cthda.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1080
Manufacturer: NVIDIA
Chip type: GeForce GTX 1080
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: EnumPCIVEN_10DE&DEV_1B80&SUBSYS_61833842&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 16201 MB
Dedicated Memory: 8079 MB
Shared Memory: 8122 MB
Current Mode: 1920 x 1080 (32 bit) (144Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.650391,0.329102), Green(0.331055,0.622070), Blue(0.151367,0.052734), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: VG248
Monitor Id: ACI24E1
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_63268710a2dc3648nvldumdx.dll,C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_63268710a2dc3648nvldumdx.dll,C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_63268710a2dc3648nvldumdx.dll,C:WINDOWSSystem32DriverStoreFileRepositorynv_dispi.inf_amd64_63268710a2dc3648nvldumdx.dll
Driver File Version: 26.21.0014.4575 (English)
Driver Version: 26.21.14.4575
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.6
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:False
Driver Attributes: Final Retail
Driver Date/Size: 3/16/2020 5:00:00 PM, 964504 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-58C0-11CF-2D4A-8D411BC2D735}
Vendor ID: 0x10DE
Device ID: 0x1B80
SubSys ID: 0x61833842
Revision ID: 0x00A1
Driver Strong Name: oem40.inf:0f066de361856a84:Section094:26.21.14.4575:pciven_10de&dev_1b80
Rank Of Driver: 00D12001
Video Accel:
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC DXVA2_ModeVP9_VLD_Profile0
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported

svyat770 [2114355] Tester 3 Jun 2020, 06:24 TCT · #16

All right.

As far as I tested this on the low-res device (<1340x600px) I've finally spot some glitched on zoom. It seems to happen only with some particular, legacy blocks site-wide.

Can someone make a list with screenshots regarding which blocks look broken on zoom? We'll try to investigate them all along. Perhaps make some fix in the nearby future.

Btw the logo is fixed now!

Thanks.

deft [979003] 3 Jun 2020, 21:55 TCT · #17 · edited

TinoMoney [2439997] 12 Jun 2020, 17:55 TCT · #18

having a layout issue as well
[image: i.imgur.com]

[image: i.imgur.com]

TinoMoney [2439997] 12 Jun 2020, 17:57 TCT · #19

NOTE: when i zoom into 125% it goes to normal

[image: i.imgur.com]

svyat770 [2114355] Tester 14 Jun 2020, 04:19 TCT · #20

Hi there! Sorry for a quite long delay with the response.

We successfully investigate the issue here. It seems to occur since Chrome v.83 and above. The rest of the browsers (like FF) in the latest version got the same problem as well somehow. You can try it by yourself, just download Chrome v.81 or less and explore "broken" pages again.

I would like to say that it's not our fall guys. We appreciate your help and will try to solve the issue as soon as possible. Besides, if you want to play comfortably along with custom zooming even now, well, you shall keep Chrome v.81 or similar closely.

That's what we have for now. Stay tuned.

Thanks.