i did the heat gun trick with my vga and is working again! it works! the heat gun works

no new vga for me untils this one is totally broken 

 

you haven't, relax 

the App knows I did it, and it's just waiting for right time to send the data packet 

Has anyone else ever been punted to some shitty fucking fake "YOUR COMPUTER HAS A VIRUS" website, when browsing quakeone.com? Just happened to me now and it's not the first time... 

 

 

If anyone's brave enough to try it, this is the link I clicked on (from a google search)

http://quakeone.com/forums/quake-help/servers-coding/10329-alternative-quakec.html

And this screenshot shows where it kicked me to after a few seconds of reading that thread - it's obviously all bullshit...

http://i.imgur.com/htjK1ir.png 

this ain't normal, is it? (see image below) I don't really see the "not secure" warning anywhere else....

http://i.imgur.com/e3wnLJ9.png 

Do you use any kind of adblocker? If not, maybe the virus or whatever it is was in some malicious ad displayed or scripted to appear on the page. This can happen even on seemingly legit websites if the ad hosting service has some of their stuff compromised.
Or maybe Windows Defender also protects the user from mental harm... being quakeone and all! 

seems to be blocking things on that page 

http://money.cnn.com/2017/03/28/technology/house-internet-privacy-repeal/ 

Whatevs. I'm more worried about him ripping up all the climate change commitments. 

dont worry, it is all gone off by now.

https://en.wikipedia.org/wiki/Clathrate_gun_hypothesis

blabla pessimisctic stuff here, we are screwed... 

Is there any major differences between Fitz, QSS, and MarkV?

All 3 seem to have the goals of

� Preserve original look and feel (crunchy pixels, twisty water)
� Support large maps (bsp2, extended limits, protocol 999)
� Support for fence textures

Is there any major defining features I'm missing or incorrect on?

What would keep, for instance, QSS and MarkV from merging? They already seem to share most of the same features and keep borrowing from each other. 

But the list of differences "under the hood" is enormous I imagine. Was just following the discussion in the MarkV thread about the differences in the MarkV renderer vs the QS renderer... 

Is the original "authentic Quake" engine, from which QS and Mark V have forked years ago.

The latest version is 0.85, from 2008. It does not support BSP2, protocol 999, or fence textures. 

QSS is not QS.

The point of QSS is to support mods. Be they qc extensions or other features that a large mod might use like particles, or merely just bigger maps, even networked.

QS (and fitz before it) on the other hand seems much more quintessential. The changes it makes are for good reason, only adding new features when someone actually NEEDS something, instead of because they might want it later, and then warning if it is ever actually used!
QS also cleans up code, like switching to SDL instead of having separate win+lin+mac ports, and stripping the software renderer (which was a nightmare to maintain).
I personally only see QS as distinct from from fitzquake because of the (significant) switch to SDL, they seem to have similar/continued goals to me and the lack of fitzquake updates kinda backs up that feeling.
QS makes for a great base engine for forks, hence the number of engines that use it as a base. It would be a great shame if someone went and just copied over all the markv files over the top.

MarkV seems to have different aims from QS+QSS, more of a sandpit than an actual goal (somewhat like FTE, but still much more limited, with many files with a single comment containing the words 'todo' in a way that indicates adhd...).
I *think* merging QSS's features over to MarkV is one of Baker's long-term goals, but I get the feeling that its a very long term one... Mostly because I don't think he gives a damn about modders as he really has no experience of qc modding.

Either way, merging stuff is never trivial, especially if someone already ported over incompatible stuff like qmb's particles instead of qss's...

Large maps/fences/etc are a product of AD and it being popular enough to get people to care about it working properly. They seem supported more due to necessity than as actual goals.
You can thank mh/rmq for it ever happening.

Ultimately though, some people just create engines because they can - its much easier to bolt your own crap on the side than it is to figure out all the crap someone else bolted on years ago.

Anyway, I'd better stop ranting before someone gets pissy about how I see things. 

I hope it returns and is more inclusive. These days everybody is after your data and personal information and seem to believe this is some kind of "right" that you must give them in exchange for using their service.

This attitude is pervasive and spans across ISPs, social networking sites, search companies, and even the Windows operating systems.

The best defense is to be proactive and aggressive in counteracting these transgressions. Use ad blockers, block JavaScript, use a tracker blocker, and even a cookie killer. A VPN maybe even become necessary if nothing is done. 

uMatrix seem to be the chrome browser plugin to control it all. "what a sentence" 

out of interest, do you have anything else on the boil at the moment?