Jump to content

S77th-konkussion

Members
  • Posts

    2977
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by S77th-konkussion

  1. there is an update for W7 users on star-force.com
  2. +1. At one time in the past- the wires were animated.
  3. Agree w/ Cosmo. I don't know all the facts about how far one can see- I suspect that can vary wildly with human factors & weather. I do know that a plane ain't supposed to "cloak" up close. I did see Yoda's comment about "model swap"- I reckon that means it's not simple to fix..
  4. FC 2.0 Crimea? What Crimea?
  5. Well like Mom said- Don't scratch it- you'll just maake it worse.. :D
  6. Top 10 Worm-burners..
  7. Several things could be the issue. Did you properly install the SST software when you installed your stick? ALL of it? Even the "magic mouse & keyboard" drivers? If you did- have you programmed buttons from within the SST software? Did you prepare the stick for button programming as shown in my setup instructions? (clear the defaults that lomac assigns) Have you been to saitek's site to determine if the SST version you have will even work on W7 in the first place? If there is SST software on the site for w7- you might want to unplug the sticks, uninstall everything you have, and install what they have on the site. From what I can see- the SST software is the same for Vista & W7. I think you will need to download both drivers & software. http://www.saitek.com/uk/down/drivers.php Read the site carefully, but it's probably something like this- Install the driver package. Possibly reboot- then plug in stick. If it prompts you to plug in the stick during the process- do it. Otherwise- reboot, plug in stick, and reboot again. Install SST software package. Follow the setup instructions on my site. The initial configuration is universal, but it's unlikely the abbreviated SST tutorial after "STOP HERE" will be applicable to the software you downloaded.
  8. Not a problem. The device shown when you enter the options menu is not the "active" or "selected" device. It's just first in the menu by default. Click sig for help in setting it up.
  9. I think the option is called Native Betty..
  10. From a purely selfish point of view- I can't get to these forums from work.. move them if you like, lol.. :D (anything under .ru blocked)
  11. It does have the AFM- put the curve where you like it. I suspect that it's twitchier because of the reduced weight compared to the T
  12. I'm thinking you are still at 1.02? If so- you really should get FC & patch 1.12 See the other thread you started.
  13. Hopefully- you installed the SST software and everything else it asked you to when you were hooking up your X52. Axis- (pitch, roll, rudder, thrust, and maybe zoom) assign these items in the lockon options\input menus. Buttons- these should be mapped within your stick's profiling software.
  14. Get the upgrade to Flaming Cliffs 1.1 and then the free patch to 1.12. Don't waste too much time training on 1.02 as the differences that FC introduced are significant outside of the most basic things. Get set up on my site- (See sig) and refer back to it for most all of the most common issues that noobs have getting off the ground. (figuratively) I will show you how to sweep away the obstacles on your road of learning & knowledge. To literally get off the ground- use ironhands site. www.flankertraining.com That's the actual flight training. There's also several banner links to Ironhand's pad on kon air, too. Read my LOMAC FAQ's. Seriously. You may even correct an issue you've mentioned already.
  15. Yep use ADI for landing. Especially carrier traps. Other than that- I don't pay much attention to it. It seems that much of the time my preprogrammed altitudes are left default by the server's mission maker.
  16. :doh:hee hee..
  17. http://www.newegg.com/Product/Product.aspx?Item=N82E16832138005&Tpk=lock%20on&nm_mc=AFC-C8Junction&cm_mmc=AFC-C8Junction-_-RSSDailyDeals-_-na-_-na&AID=10521304&PID=3747368&SID=
  18. DAMMITT!!!!!!!!!!!!!!!!!!! Edit: OK did that- box checked- but under compatibility tab it's still not checked/ greyed out.. whatever-- will try it out..
  19. Well I tried to set it to "run as admin"- but the option was greyed out in properties. I selected run as admin from the shortcut's right click menu- but who's to say it did anything? I was able to select compatibility mode, but no way to put a check in the admin box. Modman seemed to react a little when I attempted it from the rightclick menu. The CTD was delayed a bit. This time it flamed out after landing.. Screw it. I'll uninstall it for now.
  20. UAC is off- will try the run as admin... Thanks. Much as I preach this- it didn't occur to me until after I uninstalled it. Was FUMED at the 2nd crash and the teamkiller :P
  21. Since moving to new rig & Vista32- I haven't installed any Modman, mods, or any of the sort until yesterday. Got modman, installed it. Got error box saying something about In Vista 32 modman may not be 100% because I have FC installed on C:\ . Please install FC on another directory. Don't have partitioned hard drive, and not planning on doing that either- at least- not out of the blue. Maybe later, if I need to wipe it. Anyway- installed Archer's pack which sounded pretty good. The "breathing loop" was a bit loud. and just a bit short, but I like it. Last evening on 104th- On 2 sorties in a row- crashed to desktop in EXACTLY the same spot about 5 clicks from carrier touchdown. Got rid of both modman and soundpack. After having to fight off a N00b TEAMKILLER, I made another approach with no issues. Sound familiar to anyone? The particulars are: Vista 32, no mods at all other than described. Also running latest Alchemy & SB extremegamer drivers- just updated a week ago. Is it modman and the error? I didn't think modman ran all the time. The soundpack itself? or it it some combination with Alchemy? Wil "run as admin" fix it?
  22. There is that better? I wouldn't want you to feel too superior in the midst of all of the unwashed masses.
×
×
  • Create New...