Crow, Groove, Perrin... somebody

[Sinister]

I recently got the ScriptGL to work in windows 10. So all my pretty huds show. Problem is the screen flickers tremendously when i go full screen. But if i go windowed mode, only the huds flicker... help?

[perrinoia]

I've got the same problem without ScriptGL. If you figure it out, lemme know.

[Groove]

AMD video card? if so, i had the same problem with any recent AMD driver + Tribes + ScriptGL on a buddys system, only had a few hours to test and didn't have any luck finding a fix

tried rolling back drivers from Crimson to Catalyst, and tried the win update driver - all the same flickering

[Sinister]

Welp..... </3

[Groove]

there are some generic stuff you could try

running the game as administrator
trying different compatibility options (start with WinXP SP3 mode)
disable display scaling on high DPI settings
disable shadowplay
disable the 'Problem Reports and Solution Control Panel‘ and ‘Windows Error Reporting Service‘ (in services)
try disabling AA and other video options

all of my vidcards are NVidia (560Ti, GTX275 and 8800GT) and have never experienced the problem, and it didn't used to happen in older driver revisions so i'm like 98% sure it's an AMD driver issue

but i don't have an AMD to test and find a solution, for my buddy i just gave him a non scriptGL config and it worked fine

[perrinoia]

------------------
System Information
------------------
Time of this report: 3/9/2016, 18:22:01
Machine name: HANDY
Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_inmarket.160222-1549)
Language: English (Regional Setting: English)
System Manufacturer: Microsoft Corporation
System Model: Surface Pro 2
BIOS: 2.05.0250
Processor: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (4 CPUs), ~2.3GHz
Memory: 4096MB RAM
Available OS Memory: 4016MB RAM
Page File: 3230MB used, 1553MB available
Windows Dir: C:\WINDOWS
DirectX Version: 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.10586.0000 64bit Unicode

---------------
Display Devices
---------------
Card name: Intel(R) HD Graphics Family
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_0A16&SUBSYS_0A161414&REV_09
Display Memory: 2120 MB
Dedicated Memory: 112 MB
Shared Memory: 2008 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Surface Display Panel

[Groove]

idk about tribes as a whole flickering, i know that AMD + scriptGL = HUD flickering (in the scriptGL overlay only), normal configs work fine afaik

tbh any problems w/non nvidia stuff doesn't surprise me since scriptGL is based on an nvidia openGL overlay, intel has always had trouble even loading the scriptGL dll since some intel graphics dont support 100% of the openGL extensions - some are emulated with software - and intel drivers are totally hit and miss, some older drivers support things that newer ones don't and vice versa

i used to get complaints all the time about intel users + scriptGL locking up on init, but at some point that must have been fixed because i have no problems on my laptops

heck there was even a point where scriptGL would lock up for mav with the same graphics card that other people had no trouble with

tribes is old and scriptGL is finnicky, its a bad combo for modern OS's and drivers

[perrinoia]

Makes sense, except I have the same problem without scriptGL.

[Groove]

sounds like an intel issue - did u try the generic stuff i posted above? i assume flickering is some kind of frame rate/refresh mismatch caused by DWMs vsync/triple buffering BS but that's just a guess

especially if ur on a MS surface, i'd try 'disable display scaling on high DPI setting' first since im pretty sure the surface has to do some scaling to make shit readable

if none of that stuff helps i'd fiddle with the drivers/driver settings

i kinda hate intel video, i have 2 laptops that cant output HDMI @ 32bit color because intel broke it @ some point for 1st gen i-series and decided to leave it broken cause 'hey, its old 1st gen hardware, suckit'

its funny too, if you fiddle with settings enough and uninstall drivers and stand on your head during a blue moon

it'll sometimes kick into 32-bit and works perfectly until you reboot and then you have to wait until the next blue moon for it to work again

fukn intel drivers

[KILROY]

WORD!!!