In the search bar at the top right, search “t16000m” then in the results, click on the thread titled “Yet Another T.16000M FCS HOTAS Review and Setup”. I use it and it’s absolutely perfect.
Latest posts made by BobbyOnyx
-
RE: Thrustmaster T 16000M flight pack HELP WANTED TO GET IT WORKING
-
RE: JDAM and SDB issue
On another note, how do you avoid getting “horrible” ratings in campaign when your mission is sabotaged in such a way that it makes it impossible to complete?
-
RE: JDAM and SDB issue
Thank you for all your help Gentlemen, I knew the answer would be found here and yet again you’ve excelled yourselves. After re running the mission to check that I hadn’t slewed the cursor or inadvertently messed with the steerpoints I decided that it must have something to do with hitting an already destroyed target so I took off and went straight at the target at full afterburner until release point and watched the bombs using Alt 7 go all the way in.
I didn’t realise how slow the SDB’s are. It became immediately obvious that the hits I was seeing when running the mission before were not my bombs, but someone else’s, as the smoke appeared within 45 seconds of release. Watching these bombs in flight it took at least 90-120 seconds to get to target. My conclusion being, as you so rightly pointed out, was another package had been assigned the same target and by the time my bombs arrived, there were no targets left.
Lesson learned and thanks again. I think I’ll leave the campaign computer for a couple of hours before starting a mission at the very beginning to allow it time to sort itself out.
-
RE: JDAM and SDB issue
I thought this the first two times so I did purposely check and waypoint 15,16,17,18 were in the correct area which seeing as they were originally blank tells me they locked ok.
It wouldn’t make a difference that the waypoint were 15A,16A,17A,18A would it? As I set them to auto for the autopilot, obviously AP is turned off when IP but it’s a though that it might affect it?
-
RE: JDAM and SDB issue
Roger gents. I’ll try it and report back.
But from what you’re seeing I’m not doing anything obviously wrong?
-
RE: JDAM and SDB issue
JIZ indicator is half way down, I’m at angels 20
Must admit I don’t know the impact distance as I went off of the JIZ indicator and I also didn’t know CZ could be an issue, will look out for it.
Why would that affect it?
-
RE: JDAM and SDB issue
A battery of sa-2’s. I’ve never had a problem before, but I had to do a fresh install after a slight cock up on my part (unrelated) and since then I’ve tried this mission 4 times with the same outcome. I’m actually starting to think the mission is bugged.
The target steerpoints are active, the Co ordinates match the data cartridge, I power on the SDB’s, they are RDY way before release, JIZ indicator is present and lowering as I get closer, release goes well (although I did select left and right ripple but only one released?) smoke appears in the right ball park as I say but nothing.
-
JDAM and SDB issue
Afternoon chaps,
I’m having an issue with SDB’s and wanted to run it past you. It’s only started after a fresh install but during the campaign, I have a SEAD mission to attack a battery of sa-2’s. No problem, standard loadout is 8 SDB’s, I lock them as target steerpoints in the data cartridge, take off, everything going well, JIZ indicator shows, I release, smoke appears in the right area, I go to land and mission failed no hits on target.
Am I missing something?
-
RE: Connection Issues with MP
I can confirm that was the problem. Thank you again.
Connected immediately after a fresh install.
-
RE: Connection Issues with MP
Hi guys,
Thanks for your inputs. .boomer. you wonderful human being you. Although I had updates up to 5 installed and showing on my setup menu, for some reason my splash screen still had update 1 showing. I have no idea why or how that happened but it wouldnt let me reinstall them from the setup program as it says they were already installed….although they weren’t… Helpful.
Anyway, cue a full re installation and so far so good. Splash screen is showing .5 Build 16804 now so I can only assume that was the problem. Thanks for all your help. I will post back when up and running.