Sorry your browser is not supported!

What do you think is the best version for FPSC? By this, I mean, what it the most stable and best to build a game with?

I ask this because I am going to release a game within the next two months and I do not want to release a game on v120 because it's a little unstable.

Perhaps, those who have released games already can give me a bit of advice.

The best Fpsc version is 1.2 Beta 17 with the unofficial

Download this and install it
files.thegamecreators.com/betafiles/FPS_Creator_V120_BETA17a.zip

after this replace the fpsc-game.exe with this:
forumfiles.thegamecreators.com/download/2484977

I and my Testers never had any problems with this.

Corno_1

I think this is all down to what media you use and system specs.

A lot of people are having issues with v1.20 because they using older media and maps built in older versions also have lower specs and don't change any settings so it works fine on there system.

V1.20b17a with the unofficial is pretty stable now and had no problems in test that I've done and testers I use before release.

A few things people need to understand is v1.20 builds games in a totally different way than older versions.

V1.19 works well with the unofficial as well and this is what I'm using at the moment as the editor more stable for me.

If you made your game in v1.18 then it should be fine to update and make sure you update the model packs to support it.

Many people do have issues with maps built in v1.18 or lower versions updating to v1.20 due to model errors and thats because v1.20 don't like caps in the name of the models like model a.x but renaming it model_a.x should fix the problem the same for textures and all media.

I always advice that it best to try and rebuild your map in v1.20 from scratch if you can.

Make a backup of your original fpsc you using now and install a fresh copy and update.

If you have lower spec machine its best to switch off all the features that are not in early versions in the setup.ini.

Post processing =1 will eat up framerate so changing to =0 will be give you better performance like you had in early versions.


Hope this helps best s4real

Thanks s4real, I can really use that information. Really!

Also, thanks corno_1 for sharing! Unfortunately, every time I attempt to download and extract beta 17a, I get a corrupt file error from winrar.

@PixelF, I've had that happen before with winrar, but very few times, typically when the download has had some sort of error. I may be wrong, but the error may not be related to the beta itself.

I also agree on that the better version is 1.20 Beta 17a with the unofficial.

Make sure you download version 17a and not 17 as 17 has the rar issues.

I just downloaded it fine and unrar it with no problem.

best s4real

I'd have to say that 1.17 was really good as its less cluttered with semi-working and performance heavy features.

I experienced some issues with the save/load feature tough so I'd say: Use 1.17 if you can mod out some annoyances.

We use it for Canalyst.

If Blackfox shows up here, he might be able to tell you more about 1.17. They mod it and I'm sure he knows more about its "gears" than I do.



-Wolf

You have to look at what each version offers and see if there is anything in that version you may require (such as script commands for example). As each version rolls out, additional script commands are added so that helps to make a difference. Each version of FPSC is unique in its own way. While we have each version running in a VM to test, they all have their strengths and weaknesses.

V1.18 introduced water, variable system, and additional scripting features. V1.19 saw the integration of WASP mod commands and additional features for culling, weapons, camera commands, etc. Also added was scriptable post effect shaders. V1.20 added a few more features and had a lot of fixes to be done. I do not have a compiled list of what exactly was added.

The point is, each one has its pros and cons. If you do not need water, then v1.17 is more than sufficient. If you want to use the variable system, then v1.18 minimum is required. Each version runs differently than the next- you may experience some fps drop or increase depending on what you are doing. Only you will know what feels right for your work.

I would not recommend going lower than v1.17 as v1.16 and lower could not build more than 5 levels. One thing to keep in mind- when you pick your version and start a development, stay in that version. I cannot begin to count how many "issues" have been reported because people are working on a development in one version and then decide to switch. While you can switch technically, you will have undesired results with some media or scripts, or saved data. That is because each version has changes in the save/load routines that are the main cause of these issues, among other things.



There were some key reasons why we chose to remain in v1.17. First- the GUI X9 garbage. While I can understand the intent, it was totally useless. The documentation was vague at best, half the features did not work properly. I never saw one development use it. We attempted to use it and it was more of a pain to get it to work. So rather than trying to remove it from the source (it was introduced in v1.18 and it is everywhere in the source), we picked v1.17 because it was not introduced in this version. Second- ragdoll was introduced. Third- the start of DarkAI was introduced. We managed to expand on it ourselves but it was nice to have a start point. Fourth- other fixes from the older versions were made, including the ability to build games beyond 5 levels. The big one for us- this version gave us the *best* fps level compared to the rest. We do run on two laptops and two desktops and v1.17 seems to like the four machines. Even with porting water features, scriptable shaders, video textures, and other features did not affect our performance. Plus it was easier for me to rewrite the entire source code, organize it properly and add features we wanted with ease. We also do not seem to get the "collision" or other issues that have been reported in v1.19+. Mind you, I am the only one that codes our source so that makes a big difference right there. Multiple people coding can cause issues if they have their own style, etc.

In the end, it is developer choice.

After downloading it a few more times, I finally got it to work


Yes, I was thinking of going back down to maybe 1.18 or 1.17. Thanks for the info!


v1.17 does sound like it fits me best.

Thank you everyone for your posts!

Another point of information. If you do use an *older* version, be prepared to have to solve issues on your own. The chances of you getting any help with issues will be remote since very few work with older versions. A lot seem to jump on the latest and greatest, thinking the newer is better. In some cases that is true, but not in every case.

While you may encounter issues, you may find solutions by gleaning the solutions from forum posts with similar issues. Some may work, some may not, and you may have to become creative in your own solution(s). Just want to prepare you in case you hit a brick wall somewhere.

Nicely said Blackfox you covered everything I should say.

One thing to think about when picking a version also is older versions don't work very well in windows 7 sp1 and later.

I'm not sure if the updates have been rebuilt to work with windows 7 sp1 but v1.17 was originally packed with an older version of dbp that didn't support windows 7 sp1 and crashed.

I never gone back to early version so not sure if they have the problem.

best s4real

Yeah this is a BIGGIE. Unless 1.17 has been rebuilt with a newer version of DBPro, you will need to recompile the 1.17 source yourself with the latest version of DBPro, or your games will not work with Windows 7 SP1.

I had a bunch of built games that were rendered useless because they were built with the release version of 1.17.