Jump to content

Wild.Bill.Kelso

Members
  • Posts

    338
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Wild.Bill.Kelso

  1. Also, I just notice that one of my A10 skins does not have a number with the L or R: A-10-OKRAS-R.bmp.dds A-10-OKRAS-L.bmp.dds I got this skin from LockonFiles.com. It installs to the TempTextures folder. Is this ok? Shouldn't it have a number?
  2. Ok, I might look into doing that. After looking at the .bmp filenames for the A10, it looks like there are 2. a-10-okras-l5.bmp.dds a-10-okras-r5.bmp.dds So, does the number 5 in the filename indicate which skin it will replace. ie. the 5th skin? If so, at the very least, I can just make a note in the ModMan Name or Description, so I know what I am doing...
  3. Sometimes when I install several Skins for 1 aircraft type, some of the skin pieces are in the wrong place in the Game. And In ModMan some of the items are yellow, not green. I know each aircraft can only support a fixed number of skins (can't remember if it's 6, 8 or what). I am wondering if this may be because I have, for example, installed 2 Flipper skins, which can take up only one skin really in the game. Is this probably the problem? If so, how can I tell with all the Skins, several are for one specific skin replacement, or if they are for different skins.
  4. Yea, I also wish they burned and smoked much longer. In IL2/PF object smoke with a tall black column for about 3 -4 minutes I'd guess. It does add more to the realism.
  5. Got it working! I just assumed that the Mouse Axis0, 1, and 2 were for my TrackIR since 1) The Mouse Axis's were already assigned to the Horiz, Vert, and Zoom Views for some reason. I know I didn't do it. ;) 2) My TrackIR stopped working when I went into Lockon Options and changed these from the Views to the TDS. Thanks.
  6. Yea, I was setting the axis for the Mouse, not the X52. My screenshots are for my X52, so that may be confusing here. But I showed those because I am not sure where the axis really were supposed to show up. As I stated, I change the Mouse axis from the vert, horiz, and zoom views to TDS Slew, but then my TrackIR stopped working. But it sounds like you're saying that is the right thing to do. So, I'll try it again tomorrow. And if the TrackIR stops working again, I'll exit and delete that Input\TrackIR.ini file and see if it fixes the TrackIR. Ok. I had changed it to Ministick X/Y Axis (not Ministick X/Y Axis = Mouse <->) at somepoint. I think I tried both several times. But at that point I was not selecting Mouse from Lockon Options I don't think. It's a little confusing. If you click the little arrow to change how it works, the list is: Axis Bands Mouse X Axis Mouse Y AxisIf you select Axis, the description is then 'Ministick X Axis'. If you select Mouse X Axis, the description is then 'Ministick X Axis - Mouse <->' I'll give it another try tomorrow. Thanks!
  7. @rugg, Yea, I'll take a look at your snapviews.lua file and she how it works for me. @Kuky. With TrackIR it is sometimes hard to get a good look at gauges with your head moving around. Especially when you need a real quick glimpse. But Snapviews let you look exactly where you want, very quickly.
  8. Saved again by the Ruggbutt! Thanks.. I'll give this a try tomorrow. Looks to me like the keycommand.doc file is totally incorrect when it refers to the cockpit.lua file. What a lot of time I've wasted....
  9. Are you saying that the Mouse view horiz, vert, and zoom are only for External Views, and not for TrackIR at all? Because when I set the Mouse axis up for my ministick, my TrackIR stopped working. Do you have a TrackIR? And you also have the X52 Pro's ministick assigned to the TDS vert and horiz slew? Can you post a screenshot? When I am in the Lockon Options/Input for the X52 it only has 3 Axis, 1 Slider, and 3 Rotaries. The 3 Axis are the joystick x, y, and throttle. There are no other axis for the mouse. I thought I saw them this morning when it first work, but now I'm confused... I used to do this with my X45. It worked ok. But the X52's ministick is strictly a mouse. You cannot make it send buttons unless you change it to bands, and set the bands to send the keys. So, it's different from the X45. But as I stated above, the first time I started up Lockon, the ministick worked as an Axis. And to me it seemed to work much better than the keycommands. Much finer control. So, I'd like to get that working if possible. But I can always set it up as bands if I have to.
  10. I've been playing Lockon for it seems like 3 years now, and have never got this to work. Can somebody explain this to me very simple? :cry: The Lockon v1.1 keycommands.doc file says this: Alt - Key Pad 0 ------------------------------------------------------------------------- Save current camera position for the last cockpit snap view, corresponding to Key Pad 0 – 9, left or right mirror view or default view. May be different for different planes! If the user runs the mission then all new custom camera snap positions will be saved in the Config/View/SnapViews.lua file. If the user records the track then all new custom camera snap positions will be saved in the track file and then will always be used for that track in future. Note: saving snap views feature is disabled by default. To enable it set parameter DisableSnapViewsSaving = false in the Config/View/Cockpit.lua file. You may always force using default snap views by parameter UseDefaultSnapViews = true. ------------------------------------------------------------------------------ last cockpit snap view: Is this talking about the view when: holding Numpad0 and pressing a Numpad key? Or when pressing Ctrl and a Numpad 1-9 key? Or when pressing Ctrl-Keypad 0 to toggle then a Keypad key? Or all of the above?Cockpit.lua: I don't have this file anywhere in my Lockon folder. So, I created an empty one in Config\View\Cockpit.lua. ??? But following the above instructions, I viewed a Snap View by pressing Ctrl-Numpad3, then disabled my TrackIR, and used the mouse to move the view to the lower/right fuel panel. I then pressed Alt-Numpad0 to save it. It did not seem to save that view. When I pressed Ctrl-Numpad3 it was the same original Snap View. ??? I did the same and started with the Snap View holding Numpad0 and pressing Numpad3. Disabled my TrackIR and moved the view to the fuel panel again. Pressed Alt-Numpad0 to save it. Again, it did not save it. When I held Numpad0 and pressed Numpad3, it was not the view I tried to save, it was the original default snap view. What am I doing wrong?? :doh:
  11. Ok, I just got my X52 Pro, and today I went into Lockon for the first time to assign all the rotaries, sliders, and axis. I assigned the ministick x to the TDS Horizontal slew and the ministick y to the TDS Vert slew. I Flew the Su-25t and it worked great, it slew the TDS Cursor very well. So, I tried the A10, and it worked fine there as well. I few and tested it about 4-5 times, then exited Lockon. Now it stopped working! I don't know why. I have read lots of posts talking about making Bands and sending keystrokes, but it worked fine without doing this. I didn't pay close attention when I had it working, because I didn't know this could be a problem. When it worked... I am not sure if I even had a profile loaded in the X52. Or if I had my TrackIR 6dof loaded. I tried it again without TrackIR or a Profile but it still doesn't work anymore!! I was thinking that the TrackIR was seen as the Mouse in Lockon, so the ministick wouldn't be seen. Or that my profile had something set to the ministick X/Y axis, but I just don't know... I've read a few posts that say to select 'Mouse' from the drop down list, and set the axis there. But mine already assigned Axis0, 1, and 2 to View Horiz, Vert, and Zoom. I assumed for the TrackIR, so I was hesitant to change that. But I finally did change the mouse axis's to control the TDS Horiz and Vert slew. And it work, but not as good as it did the first time I don't think. But now my TrackIR did not work. So the mouse axis seem to be for the TrackIR, Because I set them back the original settings, deleted the /Input/TrackIR.ini file and TrackIR worked again. Is there any way to get this to work again?? I know for a fact it worked the very first time I tried it, but I don't remember how or why. I flew both the Su25t and the A10 several times, while tweaking the Options and flying again. And the ministick WORKED as the TDS the first time I ran Lockon.
  12. You don't have to have one. You can use your mouse on your other screen.
  13. Sweet! Thanks Rugg. I'm curious why you need to make a special one just for me. Won't the one you use work? Just curious.... PS: About 10 minutes ago I finally figured out a terrible bug that I have been working on in the Toolkit. It's been driving me crazy for about 2 weeks! I am a happy camper today!!! :megalol: Now just waiting on my X52 Pro.
  14. Well, I took the dive and order the CH Pedals from PCNation.com for $100 including shipping. The order said they were USB/MAC, and several websites I looked at also said the same and did not have System Requirments. But the CH site indicates that the pedals are for both PC and Mac OS. So, I assume the retailer is just not clear on their description. EDIT: This is what the description says on my order: 300-111 PRO RUDDER PEDALS USB MAC OS9 WHEEL ACCS
  15. Well I didn't do an extensive price comparison. But at NextTag.com I remembered that I saw the CH Pedals from $99 and the Saitek from $118.
  16. No Problem Aero.. Well, my new X52 Pro will be arriving today, and I'll be playing with that this week. But I think I'm sold on the CH Pedals. And the price is not too bad either. Thanks guys...
  17. That was a old setup. I now have the Touchscreen on the left. But the stick in still in the same spot. It's more of a height issue, as this is an old school teachers desk. And I can rest my elbow on the slide-out panel where the stick is. It's actually quite confortable. The new hotas is a Pro version of the X52. I am really sick of the 'built-in' deadzone on my X45, so last week decided to take the plunge on the X52 Pro. Can't wait to test it out and see if there really is almost no deadzone. I've actually read that there is no hardware deadzone, but I'll believe that when I use it. ;)
  18. Hmm.. I have an brand new X52 Pro on a FedEx truck being delivered tomorrow. Are the CH and X52 really a problem?
  19. Gray, I didn't see TB on your system. Is one of those 2 big monitors a touchscreen??
  20. I am thinking of getting some foot pedals for my setup. Not really sure if they are worth it because I have never had any or even tried some. 1) Do they add very much to the flight control and realism? Worth spending the $$? 2) What do you use your Rudder Lever for on your Hotas once you get pedals? 3) Can they be used in non-flight sims, like driving sims? Thanks, WBK
  21. There's some very nice setups here. Here's mine: I've got a new X52 Pro on a UPS Truck. They tried to deliver it last Friday, but I was gone all weekend. ;( But it will be here tomorrow for sure! ;)
  22. Great Find Zoltar. I've alway wondered what some of those settings really meant and how to use them.
  23. Thanks for the update Wags! It'll be hard, but I can wait for good stuff. And maybe a new pc later this year too.
×
×
  • Create New...