Gypsy Baron

I use CameraDefinition entries in my aircraft.cfg file to define the left, right and one other view.
 
I then assign them to FSX views via the HotKeySelect statements added to the CameraDefinition entries.
 
On my X-45 stick, I assign the 4 views VC (F9), the left, right and other views to the #2 hat switch.
A flick of the thumb changes the views instantaneously.
 
Very easy to implement and add to all your aircraft. I use the 'other' view as an aircraft-specific
assignment. It might be 'over the cowl' for a good view while taxiing or a closeup of the instrument panel.
 
I use TrackIR so the left/right cameras are usually down and left, down and right to see
controls on the sides of the cockpit in my single engine aircraft or the right seat and two other views in my multi-engine aircraft.. TIP 'takes care' of looking left or right 
 
In the A2A B-377 I used the CameraDefinitions to move me to the FE Station, the right seat
and the Navigators position.
 
Here are my definitions for the B-377:
[CameraDefinition.001] Title = "Co-Pilot" Guid = {8ff6c134-098d-409f-baec-caba3f683f98} Origin = Virtual Cockpit MomentumEffect = YES SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.5 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.99, 0.0, 0.0 InitialPbh=20, 0, 0 HotKeySelect=5 [CameraDefinition.002] Title = "Flight Engineer" Guid = {BBCB4E9C-ECF6-4c6c-AD83-C16084DC0B10} Origin = Virtual Cockpit MomentumEffect = YES SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.4 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.5, 0.0, -1.17 //InitialPbh=20, 0, 30.0 InitialPbh= 0, 0, 35.0 HotKeySelect=6 [CameraDefinition.003] Title = "Radionavigator" Guid = {515136DD-1A45-47c9-AF8D-C749BEEFA8C3} Origin = Virtual Cockpit MomentumEffect = YES SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.4 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=TRUE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 //InitialXyz=0.1, -0.3, -2.5 InitialXyz=-0.2, -0.40, -2.3 //InitialPbh=7, 0, 263.0 InitialPbh=-15, 0, 275.0 HotKeySelect=7 usually all you need to do to customize a view is tweak the InitialXyz and InitialPbh values.
 
 
 Paul

Create a 2nd User Account. That will have its own registry entries, etc. as long as you have FSX set up for a 'single user' in each account.  I've done that to 'isolate' my FSX install from an fsx_se install and a P3D install.
 
Another option, if you just want a different configuration for testing if make a COPY of fsx.exe and rename it fsx_test.exe or whatever.
 
The make a copy of your fsx,cfg file and rename it fsx_test.cfg (if you just run the 'new' fsx_test.exe it will create a defaulr fsx_test.cfg file.
 
You can tailor the scenery.cfg file for each fsx and simply swap them when you change from your regular fsx to the test fsx and back.
 
Likewise, if you have FSUIPC4 you can have an INI file that is unique to each fsx exe.
 
I have several renamed fsx.exe files...one for flying on the DTP "A" server, and other for the "B" server. The only difference is the IP of the server. This way I don't have to remember the IP's and re-enter them. I have a exe for Propliners, another for testing, etc, etc.
 
   Paul

File names for the Lua scripts CAN have underscores.
 
I believe what you encountered was exceeding the maximum file name length. I had run
across that quite some time ago.  I believe the max length is 16 characters.
 
All my Lua scripts have underscores in the name so I know that they are accepted.
 
   Paul