Designate target and return to search not working?
-
I cannot lock up targets, I am trying to program a controller having been away from this sim for awhile for lack of gamer computer, it used to be to a designate tgt- num 0 and num .( period) respectively to designate and return to search, I checked the forum they say use tms up or shift home to designate and use end/del to return to search, I cant get any of those to work, anyone know how I can get this working?
-
I canot speak to the keyboard commands since I both don’t know the defaults and there is no assurance that your keyboard commands are equal to the defaults. The F-16 control which is commonly used to track and untrack various sensors, especially the radar, is TMS forward (or up) and TMS aft (or down).
In short look at your controls to confirm your input activates those controls.
There are ways to confirm that TMS forward and aft are being pressed: for example switch to dogfight mode (D) and press TMS forward and aft. Repeated pressing of forward should produce a distinctive boresight cross on the HUD and FCR will have the word BORE on it somewhere. Repeated pressing of TMS aft will toggle between 30x20 standby and 10x60 radar modes. The 10x60 mode has a distinctive vertical line on the HUD.
-
I cannot lock up targets, I am trying to program a controller having been away from this sim for awhile for lack of gamer computer, it used to be to a designate tgt- num 0 and num .( period) respectively to designate and return to search, I checked the forum they say use tms up or shift home to designate and use end/del to return to search, I cant get any of those to work, anyone know how I can get this working?
Those commands don’t exist for a while now, you need to set up your commands according to the real stick functions. It’s in the manual These two specifically would be TMS up and TMS down, or rather a subset of what TMS does. By default (I think) it’s Home and End on keyboard.
-
I tried the home and end keys and got no results, not sure where to go from here.
-
Look in the setup section of the UI, in the scrollable list of keyboard commands to find which keyboard key or combination is assigned to the “TMS up” and “TMS down” callback.
-
I tried the home and end keys and got no results, not sure where to go from here.
Shift-home, sorry. But in any case, you must learn the new ways, entire logic has been reworked since your time and aligned with the real jet’s controls.
-
I looked up the UI and keyboard commands and got the same results, in fact now the radar is showing no radar returns, I went ahead and did a clean reinstall and it still doesnt work, I am looking at going back to falcon 4.33, at least it works.
-
-
- in fact now the radar is showing no radar returns, - -
What’s your FCR scan elevation (the two numbers on the cursor)?
-
-
The scan elevation was within normal limits, as was everything else, I checked scan elevation, radar switches on, and the radar looked normal except my being unable to lock tgts and then radar returns disappeared, I have since uninstalled 4.34, I am trying to install and go back to 4.33.
-
What are the ‘normal limits’ for scan elevation?
-
Presumably he means that the radar search altitudes at target range contained a known target. I don’t understand what uninstalling 4.34 has to do with anything. Some people are determined to do exactly the wrong thing and then give up when it doesn’t work.
Functional test of the TMS up and down commands is easily performed by changing of the ACM radar modes. This can be accomplished without any test targets.
-
The scan elevation was within normal limits, as was everything else, I checked scan elevation, radar switches on, and the radar looked normal except my being unable to lock tgts and then radar returns disappeared, I have since uninstalled 4.34, I am trying to install and go back to 4.33.
Sure, better go back to 4.33, but If i were you I would go back to 1.08Us
The entire community has decided to run 4.34 despite noeone is able to have any radar contact
Does that ring a bell ?
-
The scan elevation was within normal limits, as was everything else, I checked scan elevation, radar switches on, and the radar looked normal except my being unable to lock tgts and then radar returns disappeared, I have since uninstalled 4.34, I am trying to install and go back to 4.33.
Sorry dude, but in your other thread you claim to be a Falcon Veteran, yet here you apparently have never heard of TMS if you’re still referring to old num . for lock and unlock. Even more so when 90% of your threads are “this is broken” or “this is bugged” or “does anyone else have a problem with this?”.
I urge you to stick with 4.34 and spend some more time with the manuals. 4.34 is not broken here; I suspect there would be World ending hysteria on here if suddenly the AA FCR was broken to this extent. Please please put some more time in to study the sim a bit more before writing it off. I get it’s a daunting task, as there is a lot to read, but then it is a very complex jet and sim. Persistence will pay off.
-
just spit balling but had a similar experience try aN MFD swap, worked for me (blk 40). ANTENNA, SWEEP, and cursor was stuck, radar was in NORM, RF hot.
-
I had this same problem trying to designate targets and it turned out I had to have the number lock on. Otherwise, hitting shift + home or shift + end would just toggle the radios. But turn on number lock and then I’m able to lock and unlock targets.
-
depends on the altitude.
-
The issue seems to be at the interface between keyboard input and callback execution. If the keyboard input is spacebar and the callback expected to be executed is SimDoTheThing then the failure is happening there.
The file which controls the connection between keyboard input and callback execution is the *.key file. Difficulty in diagnosing *.key file issues is that they are not necessarily the same for all users. Your particular setup and upgrade history (e.g. moving .key files from a previous version) can easily lead to unexpected results. If you were to share your .key file it could be examined to see what keyboard inputs are expected to execute SimTMSUp and SimTMSDown.
-
That depends on the elevation.
-
I having same issues, i.e. i just can’t seem to lock a selected target, (im still on 4.33). I am using a warthog throttle and A-10C stick with Muds profile.
I can do everything in supanova’s video except TMS UP to select the target.
REF: Youtube “Falcon 4 BMS 4.33 Tutorial 14 using FCR in RWS mode with AIM-120 AMRAAM” by supanova.Despite me slewing over the selected target the indexer completely fails to appear and no missile will launch. Occasionally i can fire off on bore sight, of course that will normally be a miss. Yup! Its a reeeeal Goat Rope
Within the in game controls TMS up and TMS down are not in the controls list, thus it seems I can not assign to any key, e.g. shift-Home. In my copy of the manual A_A sections are omitted from the release. Any tips gratefully received, apart from the suggestion that the Airlines are Hiring!
OK… i will upgrade to 4.34 and then come back to the post. I guess the 4.34 manuals will include the A-A parts. Cheers.
-
I recommend testing the function of TMS by changing radar to ACM and using the various directions to choose 30x20 10x60 BORE or some other functions of TMS which don’t depend on radar contacts to cooperate. Otherwise you don’t know if it’s your switch or simply the physics of the radar.
If TMS bindings are not in your .key file then you should add them or change .key files.