Ebs

YES! :thumbup:

Quirk did you try this with the fixed comm.lua?

Is this any good to you? http://forums.eagle.ru/showthread.php?t=97001&highlight=6dof+russian I don't use TrackIR, but it's next on my list! :)

It's definitely something internal. if you 'enable' it correctly, dcs.log shows "unable to link target "betty" with source device"...I tried tons of stuff to get this to work. even searched through the cockpitbase dll to try and find the right link target...no go! I contacted a dev about it and he's forwarded on to someone else. if I get a reply I'll let you guys know.

How much of a tease would I be if I didn't include this :D .... ebsIR-JTAC_TrainingV9000.miz

:huh: alright I did not expect this to work at ALL... Check it out!!! I tried tons of combinations. It's all about LOS and I assume what units you use. The IR shows perfectly via the NVG. How cool is that?? And with that, goodnight ;)

Last time I tried changing the day, he wouldn't 'sparkle' at all.

that's the thing. When the JTAC replied that he was marking the target with IR, I asked the ground crew for NVG....then the bug came...Unfortunately the time range for JTAC to use IR is far too light to use NVGs anyway... :(

It was in this very thread turbo ;) http://forums.eagle.ru/showpost.php?p=1605074&postcount=113 Apparently JTAC is hardcoded to use IR pointer at a certain time. If the conditions are right, he'll sparkle. Not entirely sure if this is a bug! It'd be nice to see a fix for this from ED in future...no biggie if not though. and I'd be honored if you include the pilot note in 1.3. That'd be great. Thanks!.

Glad it's working for you guys. Spread the word! ;) Maybe the powers that be are reading this and one day it's gets a sticky. Fingers crossed :)

Nice one Turbo! My own personal fix was to comment out the first staticparamsevent function in your original file. But now I compare the 'new' file I see it's the 1.2.2 comm.lua with those two (all important) extra lines added. Cheers mate. Ebs.

Hey TurboHog :) So, here's how to reproduce this... Instant Action/Ka 50 Cold Start in Mozdok/ When you get into the pit. Contact ground crew and ask them to give you the NVG...nothing happens. Ground Power etc. works fine. it's just this one option about HMS or NVG that doesn't work. Without your mod enabled, changing to NVGs works fine. it's a strange one!

That particular mod is a great example of how many current mods are ready to go with JSGME. go into your _MODS folder. make a new folder called (e.g.) "DIVEPLANE NVG MOD" and extract the zip into that folder....enable and away you go... It's that easy! Take a look in C:\Program Files\Eagle Dynamics\DCS World\ you'll see a "BAZAR" folder. Take a look in Diveplanes zip...also a BAZAR folder. When you create a folder in _MODS that folder becomes your virtual DCS World folder...know what I mean?. It's just all about the file structure.

Right, I'm guessing you only have BS2 installed in world? I believe the female mod was made with A10c in mind. But I've changed the file structure in the mod and it SHOULD work now. I've attached a zip. unzip it to your _MODS folder...run JSGME. Enable it. And go fly a mission...Let me know if it works...

This should work for the sim --if LockOn_Options.flight.radio_assist then creators[devices.MLWS] = {"avMLWS", LockOn_Options.script_path.."Devices_specs/MLWS.lua", {{"betty", devices.VMS}}} --end (comment out the "if" and "end" lines) but I haven't been able to get it to work :(

OK Dozer, I'm more than willing to help anyone who asks. Which step did you get upto in my guide? You created the _MODS folder in C:\Program Files\Eagle Dynamics\DCS World\ right? and setup JSGME?

Please do! :)

Cheers Fangav! Just giving something back to the community, that's all :)

Not working for me either. I copied the extra folders FM/Input etc too. No "Apache" shows up for any coalition in ME. :(

TurboHog, here's a little tribute to your incredible mod. Install the mod via JSGME ;) Cheers :) PS. Remember to turn on your pilot (SHIFT + P)! KA50 JTAC Pilot Note.zip

Dozer, the point of all this is to hopefully encourage modmakers to use JSGME instead of ModMan. I tried ModMan once and found it a pain in the arse. You shouldn't need to mod your mod installer just to get it to work with DCS World or worry about red or yellow lights or whatever it is. zzzspace just released his 2.0 sound mod and most of his original post is instructions on how to get ModMan to work...followed by futher posts in that thread regarding issues with Modman..and not the mod itself. I think you're misunderstanding a key point here. You don't need to do anything extra to get a mod to work with JSGME. If the mod is packaged in the correct way by the creator of the mod then it's a simple drop in for JSGME. If a previous mod has install directions of "just unpack this zip to your DCS:W directory and overwrite" then it's ready to go with JSGME. I started this thread because I saw post after post of people getting frustrated because they had problems with modman. In those cases, JSGME is the perfect solution. Ask a mod creator what he'd rather see. His thread full of posts discussing his mod, or a thread full of posts dealing with problems with the program that's used to install the mod.

Triple post! I checked out a KA50 mod today that adds a "TV" mask to the KA50 SHKVAL and it's awesome! But the filestructure had changed since 2009 etc.... So here it is ready for JSGME...Just extract this to your _MODS and away you go! I didn't make this, I just repacked it. Full credit goes to Migo. http://forums.eagle.ru/showthread.php?t=45496

Yes, you should generate a new snapshot everytime you install a module like Blackshark, FC3, Huey, F/A-18 ;) etc... The ED autoupdates will make changes to these modules as and when required. (btw, did you test the thing I mentioned about NVG swapping with the JTAC mod?)

Dozer, how'd you think the mod gets created in the first place? :music_whistling:

NICE! Familiar...but nice! ;)