Jump to content

ericinexile

Members
  • Posts

    650
  • Joined

  • Last visited

Everything posted by ericinexile

  1. I only know two ways to make my mini-stick work: One, which is my preference, is to assign the mouse axis to the TDS, or Two, to change the mini-stick settings to "Bands" and then assign the TDS keys to those bands (which is what you must do with Falcon4:AF). BTW, everytime I've ever tried to assign the mini-stick to a Joystick axis, the Saitek software locks...don't do that.
  2. Does anyone know how to reduce the number of lines of chat that will superimpose over the screen (For instance when several players are conversing via "Cntrl-M")? Everyone I've asked says that they see at most just five lines and those lines don't extend far enough down the screen to be a nuisance. However, I get 10+ message lines which can creep below the top half, covering my HUD. This is at a resulotion of 1240x1024. Thanks, Eric
  3. Solved with DMZ. I hate to open up my computer to anyone wishes to come in but so far that's the only solution. Stay away from Trendnet routers. Thanks for everyone's input. Please visit my next thread for another unrelated problem... Eric
  4. Well obviously Andy was right. Problem is more random than I thought but, when it happens, it is always either the instant I'm airborn on T.O., the instant the wheels touch on landing, or the instant I fire a weapon. The Graphics thing had zero to do with the problem. Next try will be DMZ'ing my router, but I almost hope that DOES NOT work.
  5. Well the following is so rediculous that I may just shut this thread down by stating it. As I have said, I have flown ten times without success because I've been "kicked" to debrief either at the exact moment I became airborn or the exact moment I fired a weapon. So, I changed two things, both in graphics: 1) I changed textures from low to medium and 2) Lights from "none" to "weapons". After that, I flew for 45 minutes firing guns and missles at nothing--no unwanted debrief. Some Russian guy in a MIG29 tried the shoot me down but, as this was at night, I just turned off my lights and flew low--still no debrief. Once he was gone I did a few touch and gos just to see if I could get myself "kicked"--I didn't until I quit on my own...a first. Now I'm not saying I solved anything by changing the graphics settings but is it a coincidence that it worked for the first time after doing so? I doubt it but wanted to mention the odd "solution" anyway. Keep the advice coming. Eric
  6. Thanks. I was hoping to avoid that one but that will be my next try. Keep the suggestions coming--I really appreciate it. Eric
  7. I'm running 1.12a with a clean install. Just flew around for 15 minutes. The instant I fired guns the game quit to debrief. WEIRD! Single player--no problem. I guess it's back to F4:AF for awhile until I can find a solution.
  8. I'm sure this gets asked about once a week. It's my turn now so here goes: I have a TrendNet Router with Port Forwarding set to 10308 with UDP/TCP checked and routed to the proper static IP address. I have tried changing my /config/newtork/config.lua file timeout settings to "600" per the suggestion of a helpful HyperLobby player. I've also tried deleting the file so that it would regenerate on the subsequent network game--to fix the previously suggested fix. ...So those were the attempted solutions thus far. Here is my problmem: When I connect to a hosted game either through hyperlobby or entering the settings on my own, I get into the cockpit just fine. I (usually) can taxi just fine. Half the time I can take off. The other half the game stops and exits to debrief. On those occasions where I manage to get off the ground it flies fine and will continue to do so for as long as I just fly. I can watch other planes fly, I can get close to them, but the momment I fire a weapon even if I am just shooting up grass with my guns, the game stops and exits to debrief. No crash, no death, no explanation. Just the debrief of my takeoff time. I've been playing single player for months without any problems. I've also been playing Falcon4:AF multiplayer without any problems, once I got the port forwarding thing figured out. Any help is appreciated. XP2 Intel 2.4 1 gig NV 6600 Firewall (Norton) disabled Windows Firewall off Regards, Eric
  9. Well after gushing about 91.28 I've since had to revert to the previous driver. With the settings I was using large "triangles" of terrain would be remain blank and occasionally the pit would be partially obscured by these huge bands of...well I don't know what they were but they were obscuring. Probably this was all due to my settings and NOT the software but to be safe I went back with no problems--and not that I have a better idea what I am doing, no frame-rate loss.
  10. The real world immersion, particularly in MP, of F4:AF is amazing. I'm at a loss to understand how so many units can be operating independently without bogging the game down. However, at slow speed/High AOA the flight modeling is very weak. Although I have no time in fighters, I do have over 11000 hrs in jets and I compare notes with fighter guys all the time. F4:AF does not fly like the real thing. A DC-10 is downright sprightly compare to F4 in the low speed range. If anyone built an airplane that was that hard to land, they'd be banned from any more military contracts. The F16 is supposed to be the worlds easiest airplane to land, not the hardest. LOMAC feels real. For me that makes it better.
  11. I've experienced a huge framrate increase with 91.28. Admittedly, this might be due to the fact I've set 3D rendering to "performance" instead of "quality", something that was probably possible before, only I didn't know how. Also, the quality has definately been degraded, even on the plain desktop. In the end, it's worth it because the game was practically unplayable (with anything but a single a/c with no clouds and no collumns) before now.
×
×
  • Create New...