Quote: "I understand your frustration but as far as I know once the final of fpsc v1 is released there will be no more support for the product.
So more major bugs are being fixed at the moment, but like I said editor fixes are hard to do as we don't have much control."
The ironic thing about the issue I mentioned is that it was not in the editor portion of the code. It was in the section relating to the "userdetails.ini". According to what Lee's reply was to me, there is some code that will grey out textures and such if an invalid serial is in the file. That lead me to look at our "userdetails.ini" because I recall in past installing older packs would reset this file. We were right in the middle of testing a model pack to be released when this started. We tried in another version and same thing. We looked at the media thinking maybe we did something wrong, and all the while it was the missing username/serial (again) causing the issue.
Quote: "Scene and myself are going through a lot of the bugs but time is running out.
"
I understand, but not only do we do this as an income, we have a large investment into this software and our developments. There is no way (and no reason) to have to wait for something to be addressed in the next version or a new version, given some of these issues have been around a lot longer than others. I myself would tend to think
core issues would take a priority over features introduced at the start of v1.20, considering that these core issues existed well before. Things like files not being copied to a final build are time consuming when one has to sift through their notes and check everything has made it into a final build. As I said before, the balance of troubleshooting/developing has shifted slightly to the troubleshooting side and in my case that is time and money lost when we have deadlines to meet.
Quote: "I should say the only support for fpsc v1 will be from unofficial releases once the final is done.
"
I have made that assumption already. Recall the issue I briefed both you and Scene on regarding compiling my source, how I had to do both the "mapeditor" and "game" exe's in order for dynamic items to appear. I could not get a straight answer even from Lee himself as to why that was, being we were still in v1.17 and v1.19 was in development. Per his suggestion, we compile both and do so with each change we make to our source (which by the way does not produce near the errors we hear/read about regarding collision, entities, etc). I guess I look at it from the point with 3 developments still going in v1, we had hoped that the issues could have been solved. Since you guys are short on time, I will have to make time to address it on our end and fix it. With rewriting the entire source, at least it is much easier to see where the issue(s) is/are and is easy for me to fix. I was speaking on behalf of those that do not program/mod their source as they too have similar issues (files not being copied to a build, etc).
This in no way diminishes the hard work you, Scene Commander, Flatlander, or others have put in to fixing problems. We appreciate the effort, as do many others. It would have been nice to see most, if not all, addressed before v1 was labeled "complete", as there would be no chance of getting anything fixed after that point and one may have to start all over with the next version.
Quote: "I can't imagine any FPSC users that won't be migrating to FPSCR later this year."
Well now you can. My wife and I have three full developments running in v1 and cannot afford to scrap them and restart. We won't be in FPSCR for at least another year plus. I recon we will be one of the last "users" still using v1.
There's no problem that can't be solved without applying a little scripting.
