1 visuals.ini not loading
Hey there I am having several issues regarding saving my visuals.ini when I edit the visuals it always rewrites the orginal. I have installed fps creator to my d: drive so it wasn't due to permissions.

When I test ingame then I have to always slide the visuals again but the configuration seems never loaded. Altough I see it was written when I unload fps creator .exe and start again it just starts again with the default settings. This is very frustrating...Does any one know how to solve this?

2 changing loading screen and menu options and backgrounds
Secondly How can I change the loading screens in the compiled exe?

3 Oculus rift support not working with setting anymore
Thirdly, Why has oculus rift been removed? I would like to buy a oculus rift dk2 for fps creator...

4 Distribution and selling games
Distribution of games. When will a license system and compilling to a full.exe will be included? I am redistributing all models unpacked when building the exe...
I think we require to embed the models and resources and not have all the resources open..

Thanks in advance!

1: I have the same issue, and it's been that way on and off during this whole development process. One beta seems to keep them, the next returns them to default. They do carryover to any standalone that I make. Sorry, can't help you, but then it's a beta engine.



2: Titlesbank in the Game Creators/ FPSC Reloaded/Files directory, not the standalone. While I haven't tried changing them in a standalone, I probably wouldn't even bother because the standalone media are encrypted; not sure it would work. Feel free to try it!



3: Per Lee: @Jerry Tremble : We had to make some HARD choices for the product, and one of them was to suspend any work on Rift/DK2/Gear until we have a solid dependable core engine. I think it's the right approach as it benefits the many. Definately coming back in 2015, VR is SO cool!!



I'm looking forward to it too! Steam release estimated March 2015! It worked in an earlier beta, but it needed a little work and performance was already an issue.



4. The engine is still in beta. Not sure about a "licensing" system, but the .exe is there and all the media (as far as I know) is encrypted. (Just try editing it). I haven't checked the scripts (they weren't encrypted earlier) or other things though in this new beta. As for now, a stand alone installer should work. But then, why would you want to release anything with the current engine? It's not done!

the visuals.ini is very frustrating me.. I will please this in bugs too i had this issue since 1.8