Jump to content

Recommended Posts

Posted
It is a bug, most likely fixed for the next OBeta build.

 

Nate

 

That's good to hear, thanks Nate.

On a slightly different note I had a bugger of a time last night when trying to target a convoy of tanks. The first locked up nicely, but when trying to lock up the second it went into 'Breaklock mode' where the cross hairs disappear altogether (except for a mm or two right at the edge of the MFD) For the remainder of the mission I couldn't lock anything with the Mavs. Has anyone else come across this? Is there a way to reset them to their original state (where they have a 2-3mm gap in the middle of the cross hairs)?

 

Cheers

Tom

Windows 10 Pro 64bit, Gigabyte EX58-UD5, Intel i7 920 Corsair H70 water cooled @4GHz), Corsair XMS3 12GB (6x2GB) DDR3 PC3-12800C8 (1600MHz) Tri-Channel, Nvidia GTX780, OCZ Vertex 256GB SSD (for OS+DCS), TrackIR 5, TM Warthog HOTAS + Saitek Rudder

Posted

Yes, slew the mav and it should come right out of BL mode.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

GGT, I agree you can slew the Mav however it seems even more reluctant to lock than usual (I have never managed to get them to lock once the cross hairs have disappeared ie breaklock mode) as soon as I release the slew button they revert to breaklock mode.

Windows 10 Pro 64bit, Gigabyte EX58-UD5, Intel i7 920 Corsair H70 water cooled @4GHz), Corsair XMS3 12GB (6x2GB) DDR3 PC3-12800C8 (1600MHz) Tri-Channel, Nvidia GTX780, OCZ Vertex 256GB SSD (for OS+DCS), TrackIR 5, TM Warthog HOTAS + Saitek Rudder

Posted

Slew, TMS aft short to ground stabilize on your target. Yes, there are some issues with maverick, but that aside here is the basic way it works:

 

When you hit TMS FWD short (not working correctly yet) it forces the maverick to initiate a target search in the crosshairs.

If you slew the mav, the same happens when you release the slew.

If you don't ground stabilize after releasing the slew, the crosshairs might come off the target before it is recognized as such by the maverick.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

The way I see it, there should be NO reason to HAVE to re-designate the SPI with the Maverick.

 

I set the SPI with the targeting pod, and I want it to stay there. That's the whole point of an SPI, you can set it with one sensor, then "use" it with another.

 

If you set the SPI with the Mav, and it wanders off - there goes your nice stabilized point...

 

Slave Mav to SPI - Yes... Re-designate SPI with Mav - No...

 

Am I way off base?

Posted

Not sure what you mean... If you set an SPI with the TGP, in my findings, it "stays there." You can re-designate an SPI with the Maverick, but I don't think it just "disappears" just from switching from TGP to Mav if that's what you mean.

Posted (edited)

No, What I mean is, if you designate the SPI with the Mav, and the Maverick wanders around, the SPI then wanders around with it.

 

The SPI is slaved to where the Mav is pointing in that case.

 

If however you designate the SPI with the targeting pod, and only slave the Maveric to the target pod's SPI, If the Maverick looses it's ground stabilized position, it won't drag the SPI all over creation with it. The SPI stays put because the targeting pod "ownes" it.

 

I'm butchering the concept, but does it make sense?

Edited by polygonpusher
Posted

Does now. Only answer to that is... what does the real aircraft do? Personally I'd have no quarrel with a moving Mav SPI, since I've got LITENING around to do the job.

Posted (edited)

Wait, if you already have the spi thru the TGP, and you reset another spi with a mav, it should not mess with the tgp unless you slave all to the spi with the mav. I am thinking correctly?

 

 

Bullet

Edited by Bulletstop
spelling

I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.

Posted

Yes, and that's what I see some people recommending. . . slaving all to the Mav SPI, then locking up with the Mav.

 

That's why I disagree...

 

You don't need to slave all to the Mav's SPI in order to use it successfully.

Posted

yes, Nate has said that is the procedure to redisgnate the spi and then hit tms fwd short immediately to lock mav, but this is a bug. he has said so. it really should be slave all to tgp spi then hit tms fwd short to get mav tracking.

 

 

Bullet

I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.

Posted

Having trouble with Slave to All.

 

When I have designated a point track target with TGP, I designate SPI, I switch to maverick display, but when I try to slave the maverick to the SP1 nothing happens. I have a Wingman Extreme Joystick, with no China Hat button. I set up the Left Shift + Up Hat to be the same as China Hat Forward. It does not seem to do anything. How do I enable this, if I don't have a China Hat button?

Velocity MicroI7-4790 Windows 7 Home Premium 16Gigs RAM EVGA NVIDIA GTX 1070 500GB SSD TM Hotas Warthog

Posted

I don't know about the rest of you but why not save yourselves the headache if its bugged? Im not even messing with mavs untill they are fixed. In the mean time in this sim there is plenty to learn and not have to worry about relearning mavs the correct way

Posted

Lenny- Try slaving all to the SPI while still in the TGP page... I've never done it the other way but that always works for me.

 

 

Wait, if you already have the spi thru the TGP, and you reset another spi with a mav, it should not mess with the tgp unless you slave all to the spi with the mav. I am thinking correctly?

Yes, and that's what I see some people recommending. . . slaving all to the Mav SPI, then locking up with the Mav.

 

You guys' terminology is really confusing me. "Another SPI," and "Mav SPI" don't make sense... There is only one SPI - it's a singular thing. I have no idea what Mav SPI means, since there's only one "SPI."

Posted (edited)

Correct.

 

There is only one SPI at any one time.

 

If you set the SPI using instrument "A," (TSM up long) then you set the SPI again in instrument "B" (such as the Maverick) (TSM up long)...

 

You have replaced the SPI you set with sensor "A's" with the SPI set using sensor "B."

 

That's why I say, if you have the target centered in the SPI created with the targeting pod, why would you want to replace those coordinates by defining the SPI again with the maverick (TSM up long?)

 

Once the Maverick is used to define the SPI, if it wanders off course you have lost your target point.

 

Keeping the Maverick slaved to the targeting pod defined SPI, means that if the Mav wanders off target, you can always slave it back to the SPI again. The SPI stays fixed no matter where the Maverick seeker head goes.

 

If however you re-define the SPI by using the Mav, the SPI now follows the Mav seeker head, the SPI and the Mav are no longer independent positions.

 

That's my understanding of things in any case.

Edited by polygonpusher
Posted

Not if I understand Spi, or sensor point of interest. you can have multiple spi's but only one active at a time if I understand it correctly. please correct me if I am not :). In the explanation in the previous thread we had a short list of what was the proper procedure at the time and it went like this.

Turn on tgp pod and mav to allow to align/warm up

Find target with TGP\Set point track with tms up/fwd short

Designate as target with TMS up long

Select MAV display on mfd

China Hat fwd lond to slew to designated target

China hat fwd short to zoom in

TMS FWD Lond to redisgnate SPI with Mav <------------ Have to confirm yet wheather this is a bug or actual implementation... is a bug

TMS fwd short to track target... Thansk Nate, I kept the bloody thing :)

 

The actual implentation is the above except the tms fwd long to redisgnate the mav spi.

 

@Aceflier that is why I keep doing it as it really does work 90% of the time...

 

 

Bullet

I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.

Posted
I don't know about the rest of you but why not save yourselves the headache if its bugged? Im not even messing with mavs untill they are fixed. In the mean time in this sim there is plenty to learn and not have to worry about relearning mavs the correct way

You don't have to avoid them all together, just avoid the bugged method. There's 2 other ways to lock a Mav that work just fine.

[sIGPIC][/sIGPIC]

DCS A-10C: putting the 'art' into 'warthog'.

(yes, corny. Sorry.)

Posted (edited)

Regarding the lock ranges for the D&Gs I would suggest trying in different temperatures. I haven't tested it but in a sim such as this one this should be addressed. The colder the environment the easier for the tracker to "see" the hot target signature.

 

I have a different question however. Just to let you know, I've read the manual in regards to this issue but found the explanation "hard to understand". :)

 

How do I adjust the boresight default location? Right now I am pressing:

- ADJ ON on MAV MFCD

- slew the wagon to a new desired location on the HUD

- ENT on the Front Dash

(that's what it says in the manual)

However, when I engage a target and then I need to "reset" the wagon by China Hat Aft Short it ends up in the same default location, before I changed it...

 

Sorry if I've repeated something but I was unsuccessful in finding an answer to this.

 

Thanks

 

PS. Has this thread moved somewhere else?

Edited by Belphe

Never say never, Baby!

 

[sIGPIC][/sIGPIC]

Posted
Regarding the lock ranges for the D&Gs I would suggest trying in different temperatures. I haven't tested it but in a sim such as this one this should be addressed. The colder the environment the easier for the tracker to "see" the hot target signature.

 

Unless your target is cold. Mavericks having an imaging seeker head, and home in on a TARGET. These things see thermal contrast, so saying they home in on hot stuff is not correct. The signal processing in the seeker head trys to find things that appear to be discrete features. So, for example, a big chunk of ice on the ground during a 90 degree day could be easily targetted on because it has a very strong contrast between it and the background. Because metal transfers heat alot differently than the earth typically does, then there is usually a significant thermal contrast between a large metal object like a tank, and the ground, even if the tank is not running.

 

Personally, from what I have seen so far, the maverick does not seem to be very realistic- it is unable to lock on targets that are clearly seen in its FOV. IRL, if a human can easily see a bright, discrete, hot target in the maverick's FOV, then the signal processing algorithm could probably "see" it too. All this said, I am only in the very early stages of learning the mav, so I could be doing something wrong. Also, perhaps targets are too brightly represented in the video we see in the cockpit rather than the ability of the maverick to lock being modelled wrong.

Intelligent discourse can only begin with the honest admission of your own fallibility.

Member of the Virtual Tactical Air Group: http://vtacticalairgroup.com/

Lua scripts and mods:

MIssion Scripting Tools (Mist): http://forums.eagle.ru/showthread.php?t=98616

Slmod version 7.0 for DCS: World: http://forums.eagle.ru/showthread.php?t=80979

Now includes remote server administration tools for kicking, banning, loading missions, etc.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...