What the heck is "run_smoke_test"?
kingkuma
cancels Work: distracted by Dwarf Fortress Join Date: 2015-09-25 Member: 208137Members
cancels Work: distracted by Dwarf Fortress Join Date: 2015-09-25 Member: 208137Members
Ok, so I was messing around through the subnautica files and found this one called "run_smoke_test".
Location: E:\Programs\SteamLibrary\steamapps\common\Subnautica\SNUnmanagedData\testing (at least for me)
I ran it (it was a cmd file) and subnautica booted up.
It looked as if I had spawned in a lifepod, which was dark, and the normal "aurora" loading screen was a transparent overlay.
Once that loaded, I had spawned in a lifepod. The systems were still broke, but the comm was working (it's light was on)
For some reason , I couldn't click on anything, so I had to use the SPAWN command to get out. I couldn't pick up anything there either. I ended up dying from a gasopod (on purpose), and I respawned, just like I had started a new freedom world. The comm worked, the fabricator worked, but the systems were still damaged. Later I found a file titled "SMOKEOUT" in my steamapps/common folder. This is what it had. (WARNING - LOTS OF TEXT)
Ok, it was around 100000 chars to long to post. I put in an attached text file.
One question - WHAT THE HECK IS IT FOR?
Location: E:\Programs\SteamLibrary\steamapps\common\Subnautica\SNUnmanagedData\testing (at least for me)
I ran it (it was a cmd file) and subnautica booted up.
It looked as if I had spawned in a lifepod, which was dark, and the normal "aurora" loading screen was a transparent overlay.
Once that loaded, I had spawned in a lifepod. The systems were still broke, but the comm was working (it's light was on)
For some reason , I couldn't click on anything, so I had to use the SPAWN command to get out. I couldn't pick up anything there either. I ended up dying from a gasopod (on purpose), and I respawned, just like I had started a new freedom world. The comm worked, the fabricator worked, but the systems were still damaged. Later I found a file titled "SMOKEOUT" in my steamapps/common folder. This is what it had. (WARNING - LOTS OF TEXT)
Ok, it was around 100000 chars to long to post. I put in an attached text file.
One question - WHAT THE HECK IS IT FOR?
Comments
Text File:
It looks like the and are attempting to use pointers that are not pointing to anything (can't call Cat.meow() if Cat doesn't exist). Since both of the functions are named "Update" it can be inferred that this occurs every frame and thus the error message was recorded twice per update loop as long as that game session lasted, which explains the length of the file.
Due to the text file recording errors that seems to suggest it is a log file, a text file that records any information that a programmer would deem useful. And recording errors is very useful. Unfortunately. and don't tell us what file the error happened in or what line of code it happened on (knowing a bug is on line 556 out of 2,325 in a certain file out of hundreds is very useful). The other lines are mostly recording your machine setup to better re-create any potential bugs found or taking note of different states of the game to better discern when the bug occurs (Main menu, swimming, looking at inventory, etc).
Command:
The command 'RUN_SMOKE_TEST' reminds me of this(starts @ 6:50);
Perhaps they are related?
That's what I thought, and that's why I ran it.
It links to a phototour called ssperf.tour of someone walking around.
SM_SMOKE_TOURFILE isn't part of the code and neither is SM_SMOKE_TIMESCALE.
Could've we just be overthinking this and it's just a performance test with smoke that was removed?
I poke around things sort of like Han Solo: if it won't work, hit it harder, if not, pass me the hydrospanner duct tape. See: me noticing the cache clearing ting and milking that for all the temporary performance gain it's worth. Cases like this one are are handled much better by someone who really knows what they're into, like @pie1055 or @ant_fio (I do plan to get into programming eventually, but probably not for another year or so, the most I've done so far is some batch file tinkering, and nothing too heavy duty at that).
Fun fact: I did try to learn C++ once. Borland Turbo C++... 4.5? I was on Windows '98, or possibly Win '95, considering I think this occurred more towards mid 90s than late 90s. I installed the program, went to do I think the second lesson (or was it the first). Couldn't get it to compile. Tried multiple times, tweaking the code a bit... nada. Finally, in exasperation, I pulled out the answer manual, and put in everything exactly as the answer key had it. And, no compile. So I gave up. If I'd had access to the Internet more than ~once a month back then, I might have figured it out, but, I didn't.
A "smoke test" is an industry term for what basically amounts to a stability test.
I haven't bothered to look at it myself but from the @pie1055 said I'm guessing this is just left over from a basic, out-of-date test on various specific mechanics which are impossible to determine now. Probably something to do with what ever new mechanics were introduced at that time.
Last time I took a "computer" class, we were taught 'BASIC' and used Punch Cards...
Ah yeah, BASIC programming on the Tandy TRS-80! So many hours wasted on trash 'programming', but in the 80s as a teenager it was the bomb-diggety:
10 PRINT "I AM AWESOME!!!"
20 GOTO 10
30 END
Times were much simpler back then.
OK, now that you mention it, I *did* do that much on an old 286 using QBasic and DOS 3.20. Fun times. (: Old thing had a 720KB 3.25" floppy drive (much to my chagrin, I had to format the 1.44MB disks from my Dad's 486 before using them) and a 20MB hard disk... Tandy 2000, if I recall correctly. 16 color monitor, 640KB RAM.