Timeslip Softworks Forums
Vigilantes => Resolved Bugs => : Nomad May 08, 2017, 06:59:04 AM
-
I had a total of 106 and the soldier had 70. That gave me a 76% chance of success.
I clicked Interrogate! and then I got the Windoze thinking circle cursor (Windoze 7).
The game is locked up.
I have a fair bit of info on the City map already (lots of surveillance and lots of interrogations). Just wondering if it handles me already having the information that the interrogation might provide?
Otherwise... it might just be a crash. =)
Let me know if you need/want logs or whatever.
-
Hey Nomad! I did add code in to allow for all intel gained, but haven't managed to test it yet, so that's certainly a possibility. Please send on log file, it might help in figuring out what the problem is.
-
Where would I find that log file again?
-
Think it writes the log when you leave the application. It keeps the 2 last instances, so no worries if it's gone. Location should be C:\Users\*username*\AppData\Local\Unity\Editor
Save games work too and can be better - if you have one handy, please send it on. I don't think the save data has changed yet on this version. It will be easier when the save data stops changing so quickly.
-
I'll send you the save game then.
Just as another note... I started a new game to check the Interrogation delay issue I had the first few interrogations. I saved the Doc then did some surveillance to find a level 1 area I could start in. I found Ray before I found a suitable block. Ray got taken out and the game told me it was taking me back Home. Then it proceeded to load in my other game.
I went from failing to save Ray, to then being level 14 and having all three companions.
Edit: lol... finding it was a biatch. Luckily for me, I mistyped the name I wanted when I saved manually. I meant to type game. I missed, but didn't care.
My save game was under:
C:\Users\*username*\AppData\LocalLow\Timeslip Softworks\VigilantesV16\SaveData
-
Save game worked, very handy. Have learned a few useful things about balance (looks like there's too much money right now - you've amassed 15K!, the vigilante business is profitable), and enemy level ups might be too slow. Could you guess at how many hours of playtime you've put in to get this far?
I haven't gotten a crash yet, but will keep trying. Any ideas on recreating? Do you know what gang you were fighting and which you were trying to get intel on when it happened?
-
The money has built up because I got the investor perk, then didn't spend much. I sell EVERYTHING that I'm not immediately using. My barter skill is quite decent.
I think it will be fine once you've added the ability to build a workshop and outfit it. Now you have a benchmark to determine the costs of those features. =)
I've played quite a bit. Hours? Crikey, I have no idea. I'd guess.... err... 5-9 hours.
No ideas on recreating, because I'd done the same thing a bunch of times before. Do mission, loot, interrogate. I expect that it was trying to call up some information that crashed it. As the info revealed is random... not much help there.
Can you debug it? Maybe put a breakpoint on it and get it to give info on each grid and see if one of them crashes it. Unfortunately that's a lot of attempts, but it's the only thing I can think of.
I can't remember the gang, either Mafia or Survivalist. The info was on the Cultists... I think. If you're going to force which grids to give info on, try them first.
-
Good to know, thanks. Hmm, at 5-9 hours, the city map needs to get bigger. Was doing initial testing on the facilities today, and I used your hard earned save game cash to upgrade. Felt sorta guilty :)
Possibly linked to the post mission loot issue. Going to do a few bug fix days once am done with player facilities, then another testing session near release.
-
Don't feel guilty spending my money on facilities. That's what it's there for.
I'm looking forward to buying base facilities and upgrades.
I hope it gave you a good indication of costs (I'm hoping you couldn't afford everything ;) ).
Remember that my play time was just a guestimation. I should probably take closer note.
-
Ha, at present it's enough to get one fully upgraded (useful for test).
Where you killing enemies when this happened? Fixed an issue around incapacitated enemies - if so, will mark as check, and see if V17 resolves the issue.
-
Possibly linked issue: http://timeslipsoftworks.com/forum/index.php/topic,244.0.html - check if recurs in next release.
-
I have two team mates set to incapacitate and two set to kill.
Me and Elena are the psychos and Sam and Emilia just want to stop the baddies.
It's not specifically covered by the kill interrogation issue.
It was a full crash, rather than a pause.
Edit: Fixed spelling error.
-
Possibly related, but hard to be certain - there were 2 issues with code : some test code still in there and an issue with registering enemies as killed. If you do get a chance to try out the next version, please keep an eye out for this.
-
lol... yeah... I think I'll notice a full crash.
But, with the new version I'll see if I can deliberately stuff it up... and try to take note of what I do.
The problem with intermittent problems is that they tend to catch you when you're not really paying attention.
-
Yeah, intermittent bugs are a pain. Good chance it's been fixed, to be replaced with new bugs am currently authoring :)
-
LOL
Yeah... well... that is the nature of software development. =)
I expect it's probably fixed and I look forward to the new wave of bugs.
-
Reminds me the law of entropy and conservation of bug counts...
So looked up some other software development laws. in case being in need of optimism too:
Years of observing programs in their natural environment have shown that
"Bugs will appear in one part of a working program when another 'unrelated' part is modified."
So with v17 introducing facilities looking forward to buggy inventory!
"If debugging is the process of removing bugs, then programming must be the process of putting them in." -- E. W. Dijkstra
Hm... I see, need to keep that programming part to minimum...
Also don't overdo it with diligence, ok, because
"It is twice as difficult to debug a program as to write it. Therefore, if you put all of your creativity and effort into writing the program, you are not smart enough to debug it."
In any case, resistance is futile, as it eventually boils to
"Program complexity grows until it exceeds the capability of the programmer who must maintain it."
But don't worry, be flexible. Closing any inconvenient talking dead issues with
"It’s not a bug, it’s a forthcoming feature!"
Simply stretching A. C. Clarke's
"Any sufficiently advanced bug is indistinguishable from a feature." -- R. Kulawiec
All in all, if everything else fails, there is always at least one solution for all the problems implied in the simple truth
"The last bug isn't fixed until the last user is dead." -- S. Markowitz
Helped me.
Edit: credit.
-
Ha, really enjoyed these. The last 2 really cracked me up.
-
My favourites. Also holds for feature requests.
Meanwhile filling up address becomes mandatory for all backer tiers.