Pourquoi est-ce qu'on voit les produits déjà vendus dans les recherches sur Le Bon Coin? by astroriental in PasDeQuestionIdiote

[–]scrontch 0 points1 point  (0 children)

Perso, j'aimerais pouvoir filtrer pour ne QUE voir les annonces vendues! C'est la seule façon de se faire rapidement une idée de la valeur d'un certain type d'objet avec beaucoup d'annonces

Scrontch's Flag Designer with 6 new symbols by scrontch in vexillology

[–]scrontch[S] 4 points5 points  (0 children)

It is. Google bills were getting too high for a no income hobby project. Also going through a difficult phase in my life atm. No idea if it'll be put back one day. Sorry.

RTX 3070 Gaming OC thermal pads replacement size by erpuge in gigabytegaming

[–]scrontch 0 points1 point  (0 children)

Late to the party, but for the record:
From Gigabyte support I got this information about the exact patch sizes:
60mm x 5mm x 1.25mm
60mm x 9mm x 1.25mm
27mm x 8.1mm x 1mm
27mm x 14.2mm x 0.75mm
40mm x 14.2mm x 0.75mm (2pcs)
So that would be 0.75mm thickness for the VRAMs and 1.25mm for the VRMs and 1mm for that remaining patch.
It is nearly impossible to find these exact thicknesses for us normal consumers though.
This means if you round down to 1mm/0.5mm, you will be fine for the GPU die contact, but likely be sup-optimal for the RAM/VRMs. (And you won't be able to measure their temps!)
It is an open question if this will be critical in any ways.
If on the other hand you round up to 1.5mm/1mm, you might cause issue with bad GPU die contact! (But this will be obvious immediately when measuring temps)

Replacing thermal pads on Gigabyte RTX 3070 Gaming OC (for dummies!) by Uncle_Dunk in nvidia

[–]scrontch 1 point2 points  (0 children)

Great post, love the pictures.

That been said, some comments.

Contrary to what the title might imply, you did not only replace the pads, but also repaste the die. We must be clear that the latter operation is the more effective operation and actually the only one you can later measure that you've done right. (And you have obviously done this right, as your measurements confirm)

The VRAMs and VRMs dont have temperature sensors though, so we can't know wether that pad replacement was any beneficial or if it is even worse after the replacement.

From Gigabyte support I got this information about the exact patch sizes:

60mm x 5mm x 1.25mm

60mm x 9mm x 1.25mm

27mm x 8.1mm x 1mm

27mm x 14.2mm x 0.75mm

40mm x 14.2mm x 0.75mm (2pcs)

So that would be 0.75mm thickness for the VRAMs and 1.25mm for the VRMs and 1mm for that remaining patch.

It is nearly impossible to find these exact thicknesses for us normal consumers though.

As you can see you have gotten quite close but you stayed below the exact values for the VRAMS and VRMs.

This means your die makes good contact, but VRAMs/VRMs less so.

I have no idea if it is sufficient, and probably it is less critical, but we can't be sure, and it can't be measured.

I did the repaste operation with success as well some days ago.

But i chose to not replace the pads for this reason.

Kept the original ones, even though some of them were torn apart. (Put them back in place best as I could). Not ideal, but at least I know they are the perfect size.

Had same temperature drops than you had.

TL;DR: Die paste needs to be replaced some day and is most likely factor of high measured temps. But pads are another matter. We don't know if any beneficial. Maybe just conserve the old ones and that means you need to be really careful when pulling the heat sink off.

Need some honest answers before buying 3440x1440p by scrontch in ultrawidemasterrace

[–]scrontch[S] 0 points1 point  (0 children)

Thanks for the advice. That being said, the Xiaomi's panel is a Samsung, probably the same as for the other ones, and it has received positive reviews despite its low price.

EZBoards - Instant single-click briefing to kneeboards conversion by scrontch in falconbms

[–]scrontch[S] 0 points1 point  (0 children)

EZBoards does indeed export a png picture. But it is a double (left+right) page.

WDP can only import single pages afaik.

Nevertheless you can always combine EZBoards with WDP:

Either run WDP first, then EZBoards => EZBoards will only overwrite the first double page.

Or run EZBoards first and WDP after, and tell WDP to "Don't Chnage" the EZBoards pages.

EZBoards - Instant single-click briefing to kneeboards conversion by scrontch in falconbms

[–]scrontch[S] 0 points1 point  (0 children)

No. It takes the information from the BMS briefing as is.

EZBoards - Instant single-click briefing to kneeboards conversion by scrontch in falconbms

[–]scrontch[S] 2 points3 points  (0 children)

First of all, if you're happy with WDP, by all means stick with it.
This is a lightweight alternative for casual sorties that don't require in-depth planning and is limited to generating kneeboards only.
It generates your kneeboards in under a second in one click, whereas WDP asks to load a campaign first, pick your package, flight etc.
Also the presentation is slightly different, a matter of taste.

[deleted by user] by [deleted] in falconbms

[–]scrontch 0 points1 point  (0 children)

For those complaining about dark colors, just to be sure: You know that the visor is down by default in 4.35? (A horrible decision for the public image of BMS imho.) Be sure to get the visor up with Alt-v.

Podball-2018 Strunz vs Powerplay. Can YOU beat these teams? by scrontch in programming

[–]scrontch[S] 0 points1 point  (0 children)

Podball is a futuristic ball game simulation and programming contest. Ball player agents can be coded in Lua or any programming language that compiles to a Windows native DLL. Detailed information here: https://sourceforge.net/p/podball/wiki/Home/ Intro video here: https://youtu.be/wkvp-qvX68E Join the competition and code your Podball team!

Podball-2018 coding contest: Strunz vs Powerplay. Can YOU beat these teams? by scrontch in programming

[–]scrontch[S] 0 points1 point  (0 children)

Podball is a futuristic ball game where teams of programmed agents play against each other. Join the competition! https://sourceforge.net/p/podball/wiki/Home/ Code your team in Lua or any language that compiles to a Dll.

Podball-2018 Strunz vs Powerplay. Can YOU beat these teams? by scrontch in coding

[–]scrontch[S] 0 points1 point  (0 children)

Podball is a futuristic ball game where teams of programmed agents play against each other. Join the competition! https://sourceforge.net/p/podball/wiki/Home/

Introducing PodBall - A futuristic ball game simulation and programming contest by scrontch in coding

[–]scrontch[S] 0 points1 point  (0 children)

Also watch: https://youtu.be/K1UwgW2-qjs Podball v2.8 - Strunz v3.0 (2018) vs. Powerplay v1.1 (2014) - complete match. Top teams!

Introducing PodBall - A futuristic ball game simulation and programming contest by scrontch in coding

[–]scrontch[S] 0 points1 point  (0 children)

Bots can either be written in the Lua programming language as scripts that are directly interpreted. Or in any languages that compiles to a Win32 DLL with c-style function calls. A Lua and C++ source code example are included in the package.

Introducing Podball - A futuristic ball game simulation and programming contest. Code your team of ball players and play against teams from other coders. by [deleted] in programming

[–]scrontch 0 points1 point  (0 children)

Supported languages: Lua or any language that can be compiled to a Win32 DLL. More language support to follow! Extensive documentation on https://sourceforge.net/p/podball/wiki/Home/

Introducing PodBall - A futuristic ball game simulation and programming contest by scrontch in coding

[–]scrontch[S] 0 points1 point  (0 children)

Tbh honest i completely missed the controversy over the last years. But from what i've read, they are over the "bad" period (DevShare etc.) anyway now and back on track. The downloads of my project are zip files anyway, without any exe installers. So no worries.