OK, everyone! Thanks for your patience…! I fixed the issues introduced with my recent monogame3.5 / visualstudio2015 upgrades!
If you have had trouble with my download in the past, I expect those issues to be resolved with THIS VERSION
-I have edited the old download links, so only the newest version is available. The Newer download is SMALLER in size, about 42megs. No confusion here…
So the download is up, and I hope some of you will try or retry the demo.
-And of those who do, please share your thoughts.
It still work for me, I really don’t understand why it has working before considering what you wrote about your issues ! Sounds looks like to be ok. But I hope for you such an easy on resource game doesn’t need a high-end computer to run.
Thanks for testing again, its cool that someone cares.
Glad at least it didn’t crash, +1, but still sorry about the lag you have…
There are 2 quick things to try here, without getting technical:
Have you tried playing the helicopter to see if that has the same lag? That would be nice for me to know. (-its less intensive in the surface-collision detection, we could see if that’s the issue.)
I have actually experienced some lag on my FIRST run-through, I don’t know if some kind of anti-virus thing, or CPU-throttling or what…
But perhaps quitting to menu, and simply restarting, or simply re-launching the game could improve performance. Worth a shot.
Otherwise, it’s hard for me to be sure about much, without getting into some very specific diagnostics and dialogue about system specs and what not… I’ll assume you have other things to do than troubleshoot some lag-issue in a demo game…
-But I will of-coarse monitor any responses from other users, and definitely try to refine the code if this is a wider issue than just one machine out of a bunch. I have a lot of code-knobs to tweak when if comes to collision detection. - Maybe I could refine some code or even cut some corners…
Thanks for testing to you too. I really appreciate any and all feedback. I am hoping for a wider range of feedback to gauge hardware requirements vs current available standard… I can change things in my code if performance is a wide issue.
Yeah, the text-reader disregarded my comma to read ‘0,9’ as ‘9’… The new text reader requires the format ‘0.9’…
-Which could be a real issue for anyone loading stuff from txt, which I used before I learned XML…
You have to go back and change all those old txt files for monogame to read them right
I just always thought it was cool to save stuff like settings as a txt, so it was easily accessable to the user.
for manually tweaking and stuff…
Regarding text reader thing, perhaps it is because you use some kind of localized reader (as comma and dot are used to represent decimal number or money amount), you could also use type.Parse() (with float/double type) or some kind of library for config file (INI style).
Yeah, I was thinking something like that. But its impossible to pinpoint, given my total system refresh… Everything from my windows to my visual studio and my monogame was upgraded. But no matter, it is corrected now.
I tried the game and I thought it was pretty cool. It worked perfectly on my machine. (It’s a beastly laptop with an i7 and two gtx 980m, 16gb ram, probably not much help for targeting performance lags )
My only real input is that maybe the controls should be listed in the settings menu.
I beat the level, I wasn’t sure what was factoring in to how many lives I had. Sometimes I had just two lives and then on some play throughs it seemed like I had more lives than that…
Hey! You were right about the controls needing to be listed in the game. So now they are
There is a new download available with that and other changes. That and more in this threads linked subjects.
)