custom cam

[Ratchet]

Hey, , I can't seem to fix this, I've even tried putting this in user.cfg.
Every time I start, the camera_custom_rise settings reset.
I can't seem to get my custom cam stay at my settings, help please?!

[Lucifer]

Put them in your autoexec.cfg file.

[MikeyW]

What exactly do you do?

I have made a file called autoexec.cgf and written things like "camera_custom_rise 8" but that doesn't work, it still resets to 6.

[Concord]

I know this is not good practice, but you can also directly change the value in settings.cfg

[Mkay1]

Why is that not good practice? If the shoe fits, wear it.

I couldn't get flex's cockpit to work, for some reason.
So what I did was download it directly and put it in resources.
I did have to change the way to access it, but it wasn't difficult.
Now it works

[sinewav]

Why is that not good practice?

I think it's because many average computer users are not in the habit of backing up files or taking good notes when setting preferences like this. They make a mistake, can't trace their steps back to find out what went wrong, then get frustrated.

Here is an interesting idea: What is Arma ships with another, empty file called "customize.cfg" that automatically gets INCLUDED from settings.cfg - or something like that? In the future we can tell people to simply look for that file, open it, and type/paste their settings in there. (It's apparent from this thread that some people have a hard time making an autoexec.cfg.)

Just a thought.

[Concord]

Why is that not good practice?

I don't know why either, I'm no programmer.
What sine wrote might be close to correct.

[Z-Man]

Mistakes the user makes and doesn't know how to undo without a reinstall are a thing, yes, but the main reason is that an update of AA will overwrite your changes. And yes, we can try to create settings_custom.cfg if it doesn't exist yet, with a 'your settings go here' header.

[sinewav]

And yes, we can try to create settings_custom.cfg if it doesn't exist yet, with a 'your settings go here' header.

That's pretty much exactly what I was thinking. I have INCLUDE settings_custom.cfg as the last entry of my settings.cfg.

[Phytotron]

Serves the same purpose as autoexec.cfg, dudn't it?

[sinewav]

Serves the same purpose as autoexec.cfg, dudn't it?

Yeah. But if a future version of Arma comes with a blank settings_custom.cfg, then the user is saved the trouble of creating the file and putting it in the correct directory. This is obviously a problem for some people.

[Phytotron]

Serves the same purpose as including a blank autoexec.cfg, dudn't it?



By the way, Mikey, attach your autoexec.cfg so we can see if you've done it correctly.

[sinewav]

Oh I misread. Yeah, the name is arbitrary. It can be called aweshaxfile.cfg for all I care.