Jump to content

A101Wayz

Members
  • Posts

    151
  • Joined

  • Last visited

Posts posted by A101Wayz

  1. Please, don't take this the wrong way, but I don't get why some people use the variable in its own declaration (I'm assuming this is meant to be the full declaration of the variable BombingRange).

     

    Is this meant to "isolate" RANGE:New() or something like that?

     

     

    The purpose of this thread is to induce Mission Creators, those who use ONLY the ME to create their missions, to take that leap to scripting. I've seen some incredible missions done only in the ME. But those same missions can be easier accomplished (in some cases) using scripting.

     

     

    While your examples will work, they can be difficult to understand to a newcomer.

     

     

    I subscribe to the theory of K.I.S.S. - Keep It Simple, Stupid.

     

     

    I have used your first example quite often, but with my example, it's clear that those method calls can be separated, or made conditional. It makes the logic easier to follow. And it makes debugging much easier.

  2. You can also set up a fairly complex bombing range - complete with an F10 Radio Menu, ability to mark the targets with smoke, and a scoring system. All by dropping a handful of statics in the ME, and adding these four lines of code:

    local bombing_targets = {"Conex_NW","Conex_NE","Conex_SE","Conex_SW","CenterTarget"}
    BombingRange = RANGE:New("My Bombing Range")
    BombingRange:AddBombingTargets(bombing_targets, 50)
    BombingRange:Start()
    

     

    In this example, 5 statics are named according to the names in the first line. The "My Bombing Range" in the second line could be any random string to name the range.

     

    I was hesitant to learn MOOSE at first simply because I had zero experience with the Mission Editor, no experience in Object Oriented Programming, and no experience with MOOSE. But, the time I spent in learning to script was more than made up for in time saved using just the ME to create missions.

  3. On the right hand vertical console, there's a switch to mirror jester's TID display in the front seat. (I'm not at my PC right now so I can't remember the name on the label of the switch)

    although you will only be able to see what your RIO sees.

     

     

    Additionally, you can use the Data Link and set an AWACS as host. Let the AWACS be your eyes.

  4. Could have something to do with the Saitek version of the X56 Rhino. I bought one and it would randomly "jitter" the throttle, but ONLY when I was flying helos. Made landing a little interesting.

    Returned it and bought the Logitech version and have had zero issues since.

    Note: when switching the sticks, I did not redo any bindings, and am still using the bindings that I had set up with the Saitek.

  5. Occasionally, I'll see a duplicate menu item on the Jester wheel... Most notably when asking him to tune a radio. For instance, I tell him to tune the DL to AWACS... When I get to the page that lists all available DL channels, the AWACS will appear twice and the two choices are identical.

     

     

     

    Anyone else experience this? Is it a bug?

  6. I really enjoy the authenticity of the F-14. Heatblur did an amazing job at making it look and sound as if we are sitting in the cockpit of a supersonic fighter. But there are things that just can't be modeled in a sim... You can't make it feel like you're in the cockpit. You can't feel the G-Forces as you accelerate, decelerate, climb or dive. You can't feel the minute pressure changes. With that in mind, I'd be all for a user selectable option that could put a digital readout of KIAS somewhere near the HUD... Not necessarily a part of the HUD display.

  7. Trying to let a friend sit in the RIO seat. But, when he tries to select the slot, the accept button on my screen is greyed out. And when I try to be RIO for him, its the same problem. The server is Updated, both our game installs are up to date... What are we missing?

  8. On the other hand someone could tell me how to assign a key to the "launch bar" while nothing in the commands refers to this thing.

     

    On the left vertical console just left of the gear lever is a switch labeled "STRUT". Hold it down and the Cat will kneel, you can see it lower, when looking out the canopy. Then just hit U to hook up like in the Hornet and off you go.

  9. For all the Steam users out there...

    Is there an easy way to switch between the OB and Stable Release?

     

    Reason I ask: I have friends that aren't very keen on the word "Beta" so they refuse to install the Beta version. And I have the F-14B, which can only be played in OB. So, if I want to fly with my friends, I have to opt out of the Beta version, wait for a 60+GB download/install and then join them. To get back to my F-14, I have to repeat the process.

     

    It's quickly getting to the point where I'm gonna have to choose between friends and the F-14. They are really good friends and all.... But... It's an F-14! :pilotfly:

  10. Extending the launch bar (Nose strut) locks the nose wheel in straight. You won't be able to steer the bird with the launch bar down. The launch bar (nose strut) is only for launching from a carrier. What you are looking for is the Nose Wheel Steering, which as previous posters have said, is the 'N' key or the pinky button on joystick ( if mapped )

  11. You'd have to place regular units for the labels to show up, AFAIK. If you don't want them to move, you would need to give them a hold command, (and if you don't want them shooting back at you) set ROE to weapons hold, and Alarm state to green. All done with advanced waypoint actions.

×
×
  • Create New...