wowbagger

But the most versatile!

I really like the ability to easily hide/unhide the controls + seat. Great idea.

Cheers Ironhand. Very happy to see this kind of thing happening by now.

If you still need people, I can help out. I have had mission restart crashes consistently since 2.7 dropped. I don't however seem to suffer crashes from just options changes.

The problem is that whatever we try seems to work for a day or two... or three and then something causes it to stop working and the crashes return. I tried the page file trick which worked for a while ... and stopped working, then I moved my page file to a different drive which worked for a while ... It does feel like a memory management issue of some sort. But my guess is that this is beyond some little trick that one of us is going to find. I'm far more than ready for ED to offer something beyond 'we are unable to replicate the crash' .. as I'm sure are they. Time to start building some more test beds and/or bringing in some more beta testers who are able to replicate the crash.

When it isn't crashing, the game should delete all the bin, txt, and ~ files upon exit. Any of those that are hanging around in the TEMP folder are there from a previous crash.

Oh, I so hope that becomes the definitive solution. I would love to see what ED does with that.

Cheers.

I just checked that mission, Flappie, and you are correct. This mission doesn't seem to dump anything into the TEMP folder that would override your custom snap-view settings. And, when I fly it, my views work properly. So your problem must be rooted somewhere else.

Hmmm... Maybe check those files in the TEMP folder and open any non-zero files to see if they contain view settings. I had it happen with a couple of different missions, in different ways, and one definitely had view settings in a strange and unexpected file from which the game was reading the view settings - I thought it was a lua file but it might have been a ~mis file.

Check the TEMP folder. If a mission dumped this dumb Config folder in there, it may still be there - in which case the game will read the views from that Config folder instead of your own defined views for all missions. I also had lua files with strange names show up in the TEMP folder which also had view settings inside and which over-rid my own settings. Just clear out the TEMP folder to solve this issue, if that's the cause. I think custom snap-views are buffered until you exit the mission, at which time they actually get saved to your SAVED GAMES folder.

Yes, Ironhand is correct. My experience is the same. And deleting the temp and shaders folders is the only thing that seems to minimize the crashes, but not prevent them.

Correct.

Yes, for that switch you would need a three position maintained toggle switch to work properly. The best you can do is set: lifting the guard = ZEROIZE Switch cover - OPEN press toggle up = ZEROIZE Switch - UP press toggle down = ZEROIZE Switch - DOWN Nothing else will work with a momentary toggle to get you all three options; OPF,OFF,DATA.

Will do.

As far as I can see what you are describing is a physical momentary toggle switch trying to simulate a virtual maintained toggle switch. You would need a button to activate twice in each direction. With the guard toggle we can go up twice (1 = lift guard, 2= press toggle up), but only down once (close guard). The only option is just using an unguarded toggle - up-up, down-down. If that's not what you meant then I'm at a loss.

I guess I don't understand then. If it's three seperate positions -guns -off -camera then it can't be momentary, because it will always snap back to off.

If the assignments are designed for a maintained toggle switch I don't think there is anyway to replicate it with a momentary toggle - even if you assign logical buttons to on and off of both poles, the switch will still always flick back to the centre position. I've always been surprised that Virpil never puts any maintained toggles on their controls - even one or two would be quite useful and leave the rest as momentary toggles.

Progress!

If I understand correctly, RogSimu seems to have been getting the crash even with compatibility 8 mode enabled, and deleting the scripts folder fixed that. I may be wrong though.

I don't have the F-5, but are those assignments designed for maintained toggles rather than momentary toggles?

Tried that, it didn't seem to affect things.

Edit: nevermind, doesn't work. Can anyone with an nVidia GPU try disabling Threaded Optimization and see if that does anything for 2nd mission crashes? I have been having luck with it so far. Cheers

Exactly! Nicely done.

In case anyone hasn't already figured this out, one thing I found useful was to map two more logical buttons to the T7 and T8 switches so that they activate when the toggle switch moves to the middle (physical off) position. This provides buttons to use by just lifting the red guards (for example, lifting guards = fire extinguishers, pressing the toggles up = eject). Or it could be useful for master arm on/off using the red toggle guard, etc.