Gypsy Baron

Members
  • Content count

    268
  • Joined

  • Last visited

  • Days Won

    10

Gypsy Baron last won the day on August 20

Gypsy Baron had the most liked content!

Community Reputation

10 Good

About Gypsy Baron

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    Daly Ciry, California
  1. Fr. Dane, Great. Glad you have it working! I'm always happy when I can help! Paul
  2. Where are those view definitions located? In the Camaera.cfg file or the Aircraft.cfg file. According to the P3DV4 SDK it appears that camera definitions in the Aircraft.cfg file can be defined just as they were in FSX and prior versions of P3D. That is, using the same templates that I posted above for the CameraDefinition.001 thru .003 views, This is completely separate and different from the global user defined cameras located in the Camera cfg file. Try adding one of the definitions I posted above into one of your aircraft.cfg files and assigning the view number to a switch in the Controls menu. That will tell you if this method is still valid. Paul
  3. After a bit of searching I have concluded that to use the View camera select assignment feature via the HotKeySelect method the camera definitions must be of the 'aircraft' type, not the 'global' type as your example shows. This means you would need to create the camera definitions in the aircraft.cfg file as opposed to the camera.cfg file. They will be rather straightforward entries and not the overly-verbose XML variety that I tend to avoid whenever possible! Here is an example of three of my definitions which I use, customized for each of my aircraft types that I fly: //---------------------------------------- [CameraDefinition.001] Title = "Right Seat" 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.7 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.8533983, 0.0, 0.0 InitialPbh=0, 0, 0 HotKeySelect=5 [CameraDefinition.002] Title = "Center Panel" Guid = {195EAB58-9E4A-2E2A-A34C-A8D9D948F078} Origin = Virtual Cockpit MomentumEffect = YES SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.7 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.4, 0.0, 0.0 InitialPbh=5, 0, 0 HotKeySelect=7 [CameraDefinition.003] Title = "Engine Controls" Guid = {195EAB58-9E4A-3E2A-A34C-A8D9D948F078} Origin = Virtual Cockpit MomentumEffect = YES SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = FALSE AllowZoom = TRUE InitialZoom = 0.7 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.4, 0, 0 InitialPbh=50, 0, 0 HotKeySelect=6 I simply use these as templates when I wish to create custom views for new aircraft and simply modify the initialXyz and Pbh values for the new view. Other changes could be the origin, title or any of the listed parameters. The GUID must be unique within the confines of the aircraft.cfg file but not globally since these definitions are only loaded for a particular aircraft and are discarded when a new aircraft with its definitions is loaded. The editing/creation process isn't too difficult but I find that during the process it is helpful to have a key combo assigned to the 'Aircraft(reload)' control in the Buttons/Keys menu so you can reload the aircraft.cfg file and observe your edits/changes. These definitions go into the aircraft.cfg file just below any existing 'CameraDefinition.xx' views. If there are pre-defined CameraDefinition.001 thru .003 views, then simply add your new views below them, keeping the numbering consecutive. Hope this helps. Paul
  4. //---------------------------------------- [CameraDefinition.001] Title = "Right Seat" 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.69 SmoothZoomTime = 2.0 ZoomPanScalar = 1.0 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=100 HeadingPanRate=100 InitialXyz=0.8533983, 0.0, 0.0 InitialPbh=0, 0, 0 HotKeySelect=5 NOTE: The above is one of my CameraDefinitons. The Copy/Paste feature on this board insists on putting it at the TOP of the post rather than the bottom so read on then refer back to the above! ------------------------------------------------------------------------------------------------ I don't have P3DV4 but I have FSX and P3DV3. If there are the same 'View camera select 1 through 9 in V4 then simply add this line to the end of your camera definitions: HotKeySelect=5 or 6 - 9 Then assign the button/switch you want to use for that view in the simulator Controls menu for the like-numbered view: View camera select 5 for the above example. In FSX some of the lower numbered views, 1-4 are pre-assigned I believe so I always use 5 on up. Typically I assign my left and right seat views pluse 2 otheres to my #2 hat switch on my joystick. That way I can 'move around' the aircraft with a flick of my thumb. If you have a registered version of FSUIPC you can expand the 4 views to 8 using a 'conditional' assignment, say with or without the stick 'pinky switch' set. In my setup the 'left' switch is assigned to F9, the VC defualt view (left seat). The rest use the HotKeySelect method. EDIT: I just looked at your definitions file. I do not use that method to define cameras but instead define them in the aircraft.cfg file so I am not certain how to maake the assignment using your 'global' method. Paul
  5. Ah, thanks for the diligence and finding the cause of my issue. I would never have seen this on my home machine as all the controllers are present, whereas here on my traveling laptop I only have a Logitec G3 keyboard attached periodically and recently added the MadCatz joystick. I have far fewer axis on this setup and I didn't attempt to 'clean up' the ported over INI file. Paul
  6. "so, the only one which seems wrong is the Axes one. Right?" Yes, that is correct. Paul
  7. Pete, Just to be clear, that INI file is the one that exists on my home computer and not the one that I have here on my traveling laptop, which I am attaching here. The previous file was to show the size and structure of my edits as an understanding of my 'reluctance' to make any changes in my methods :) The attacked INI here shows the sections related to the C172 that were added at the end of the file and dis not appear to honor the ShortAircraftName. Paul FSUIPC4_MP2A.zip
  8. Up until the day before yesterday I had not needed to make any changes/additions to any of my aircraft sections that are contained in the INI file. I am currently traveling and on my gaming laptop and an INI file copied over from my home system. I had need to do some Lua scripting for someone on the A2A forums and that called for some additions to the axis and keys sections of the A2A C182. That is when I discovered the issue. On my home machine I have a great many of the previous FSUIPC4 downloads saved in an archive and once I am finished with my travels in late September I could see If I could narrow down the point at which the aircraft specific issue began. Until then I can live with just editing the INI file when necessary. As I have hundreds of hours invested in edits of my INI files, most of which exceed 6000 lines, And all my entries are indeed 'aircraft specific' as they make use of MCRO files for each aircraft, defining the L:Vars for that aircraft, and use Lua scripts that are unique for that aircraft. I don't 'view' my INI in a 'broad' aircraft type or other identifier nor can I group or combine the various INI sections into anything other than the 'aircraft specific' architecture. I was/am reluctant to attempt any wholesale changes to the architecture that I have currently. At some point in the distant future I will move to P3dV4 or whatever version is current at that time. Then I may consider changing to the 'profile' architecture. I have attached my 'main' INI file that resides on my home machine so you can see the methods I use. The INI file on this laptop is 'similar' but the various controllers are missing and a single MadCatz joystick is in use. Also many of the aircraft referenced in the laptop INI are not installed so going through it would be a challenge at best. Paul FSUIPC4_MP2.zip
  9. "Sorry, you have profiles defined but you aren't using profiles? I'm confused. " Now I am confused. Where do you see that I have profiles defined? Does this entry "UseProfiles=No " negate the use of profiles? The sections [Keys.C182_VH-DLL] and [Axes.C182_VH-DLL] were created when I made assignments with the 'Aircraft speciific' box checked and there was already a [Axes.C182] section but it was ignored. I never use profiles nor do I wish to. All my 5600+ lines in my INI file were created using 'Aircraft specific' settings. Yesterday was the first time I came across this issue so I couldn't report it sooner. For the time being I'll just edit the [Keys.C182_VH-DLL] entry to be [Keys.C182] and move the line 0=FS,256,F,x020066D0,0,0,0 -{ FSUIPC: offset word set, offset 66D0 }- to the existing [Axes.C182] section where it should have gone to begin with. Paul
  10. Hello Pete, Somewhere along the way there seems to be a bug that crept into the code related to ShortAircraftNamesOK=Yes and the Aircraft specific setting for Axis and Keys. Buttons and Switches seems to still be OK. I am running FSUIPC4 4.97 on Win7 Pro X64. Here are the entries I made today8 to those three categories while in the same aircraft: My recent Buttons inputs, Aircraft specific went to the correct place. [Buttons.C182] . . 220=PF,13,CL38:K,0 -{LuaKill DispC182 (Flag 0)}- 221=UF,13,CL53:K,0 -{LuaKill C182_Visor (Flag 0)}- 222=PF,0,Cx510066D2,x00020001 -{offset byte cyclic inc, offset 66D2 (Incr=1, Limit=2)}- 224=RF,38,C65680,0 -{VIEW_LEFT}- 225=RF,34,C65676,0 -{VIEW_RIGHT}- My Keys and Axis inputs, Aircraft specific did not. [Keys.C182_VH-DLL] 8=48,9,x510066D2,x00020001,L53:R,0 -{shft+0: Press=offset byte cyclic inc, offset 66D2 (Incr=1, Limit=2), Release=Lua C182_Visor }- [Axes.C182_VH-DLL] RangeRepeatRate=10 0=FS,256,F,x020066D0,0,0,0 -{ FSUIPC: offset word set, offset 66D0 }- -------------------------------------------------------------------------------- And the two ini file lines related to the operation: ShortAircraftNameOk=Yes UseProfiles=No There was an existing [Axes.C182] section in the INI but the new assignment created the one above which has the full aircraft name, as does the newly created Keys section. Not sure when this issue began but it was present with 4.959n which I had on this laptop until I installed 4.97 yesterday. Paul
  11. Great. The lua display feature isn't critical to my scripts but they do help me to know which of 8 or 10 groups of controller assignments I have currently set and the assignment for each of my 10 switches on my throttle quads.my switches or in other scripts what elevator trim or rudder trim I have dialed in and myriad other settings/states. Paul
  12. Pete, will FSUIPC5 retain/include the lua capabilities that we currently have in FSUIPC4? Paul
  13. Always happy to share the bits and pieces of the FSX puzzle as I discover them :) Paul
  14. I have my fingers crossed :) I have untold hours invested in creating my 'aircraft specific' sections with heavy use of conditional statements to allow the 10 switches on my Saitek Pro throttle quadrants to have up to 10 unique assignments for each switch for each aircraft. All of that has to be done by hand edits of the ini file. When Pete added the auto-comment feature that made life easier for me in following my own coding and not having to add my own comments as I had been doing all along! Currently I do not have to use the keyboard or mouse to any extent to fly any of my aircraft from cold & dark to in the air and return, thanks to FSUIPC4. I have lots of hours invested in lua scripts as well Paul
  15. That is a game killer for me. There will not be any Dovetail products in my future. That is for sure! Looks like P3DV4 will be my path once I decide to give up FSX. Not looking forward to having to regenerate the 7259 lines of my current FSUIPC4.ini file! :(