moggel

I wrote some logic that tracks hits (listening to S_EVENT_HIT event) for scoring purposes and that logic also records weapon type, mainly to filter out anything that's not bullets. But I later realized that when I run the script on a server the `weapon` field is missing from the event. Is that by design and, if so, why? Is there a way to work around that, or ensure the data gets sent?

Sorry. Might be we've mistakenly downloaded an older version then. Where can I get your corrected version?

I recently learned (from a squadron mate) that the VPC mod causes integrity check issues on servers (with that feature activated): textures/su-27_detail @ c:users/username/saved games/dcs.openbeta/mods/tech/vpc-airfield equipment 0.9.4 beta/textures/vpctextures.zip Are there plans to resolve this? I really like this mod but right now I can't use if because it would just be too much of a hassle for the guys in my org (DCAF) to keep adding/removing the VPC mod as they want to join non-DCAF servers.

I updated yesterday and didn't realize yet another version was out there. Updating again now and that should likely fix it. Thanks!

purchased Sinai a little more than an hour ago. Restarted DCS several times I'll let the screenies talk...

Seems to be working now!

I can confirm this happens for me too. Also, my org's servers won't come up after the upgrade due to authorization issues as well. Seems to be an ED server issue

In my group (DCAF, 119th FS) we specialize in Wild Weasel mission and rely on the HTS for our Hunter Killer hops. In such we try to filter the HTS classes to remove uninteresting emitters and lower the HTS scan times. With all classes active the HTS scan times are well over a minute whereas if we filter it to one or two classes the scan times are reduced to under 10 seconds - quite a difference when you're traveling at 350-400kt, trying to build SA. However, I have seen no real difference in how fast the HTS picks up an emitter, regardless of the current filtering. This makes me think that feature is just cosmetic at this point, and is yet to be modeled. Can anyone chime in with more insight on this topic?

Yep. I need to up my game in the visual arena, that's for sure.

Been doing some PvE BFM hops lately, to improve my abilities in the visual arena, and some of that has been vs the Mig-21 (skill = Ace). That thing often out rates me, even close to Viper's corner speed. Is it bugged or is that actually realistic?

It was me misunderstanding Thrustmaster's docs, it seems. I mistakenly assumed that the driver package I downloaded would cover all detected Thrustmaster devices but, apparently, it did not. It only supported the Warthog HOTAS and TPRs, not the Cougar MFDs. I ended up uninstalling TARGET, then all Thrustmaster drivers and started over. After having installed the HOTAS drivers and then the Cougar drivers I unplugged everything and installed TARGET. A reboot, all devices plugged in, and now it works fine. So, the usual combination of user not reading up carefully and really really louse error messaging. As always. Also, I have to say that even though I really love Thrustmaster's hardware it really isn't very Plug'N'Play. Thanks for trying to help out guys!

- Tried setting all '1' to '0', in USB registry, as per instruction0 - Remove TARGET and TM drivers, then rebooted - Installed TM divers - Unplugged TM devices - Installed TARGET, then rebooted Still get the issue If I unplug the MFDs it seems to work Tried commenting out the MFD mapping in script and rerun TARGET (with MFDs plugged) but still get the issue Tried starting a new empty script. Still get the issue So: I can't use TARGET with MFDs plugged in, for some weird reason

I had to do a clean Windows reinstall to resolve an other matter. I saved the .tmc scripts, of course (a lot of hours have gone into that). But after the ireinstall, the Thrustmaster driver and then TARGET sowftare installation, when I run the .tmc the script fails with this output: Running script: D:\Thrustmaster Warthog\DCS\Warthog f-16c\DCS F-16C.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[5]: 1: "TPR T.Pendular Rudder" - "USB\VID_044F&PID_B68F&REV_0110" 2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" 4: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 5: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&153678D8&0&11) selected USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&153678D8&0&12) selected USB HID device with hardware id "VID_044F&PID_0403" cannot be found USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\6&15B8B68D&0&2) selected USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\6&15B8B68D&0&3) selected USB HID device with hardware id "VID_044F&PID_0400" cannot be found USB HID device with hardware id "VID_044F&PID_B10A" cannot be found USB HID device with hardware id "VID_044F&PID_B10B" cannot be found USB HID device with hardware id "VID_044F&PID_B687" cannot be found USB HID device with hardware id "VID_044F&PID_B679" cannot be found USB HID device with hardware id "VID_044F&PID_0405" cannot be found USB HID device with hardware id "VID_044F&PID_0406" cannot be found USB HID device with hardware id "VID_044F&PID_0407" cannot be found USB HID device with hardware id "VID_044F&PID_0408" cannot be found USB HID device with hardware id "VID_044F&PID_040A" cannot be found USB HID device with hardware id "VID_044F&PID_040B" cannot be found USB HID device with hardware id "VID_044F&PID_0409" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse (absolute axes)...Done main returned 0 Error:One of the selected USB devices (2) has been unplugged. Aborting script! Aborting script (check output above for reason)... Script stopped! Any idea what's causing it, and how to fix it?

Some more experimenting with this. My problem was, I believe, not that I couldn't boresight but that I often failed to get teh Mavs to make the lock. That seems to have been me not ensuring all Mavs where in the zoomed-in state. Once I make sure a Mav is zoomed in properly it seems to accept a handoff (mostly) and lock successfully.

I did not. Thanks mate!

Yes, I suspect so. I sent a DM to Ranger, hoping he can maybe do that

I tried creating a "Liferaft" folder, then moved the folder structure (./Shapes/*, ./Textures/* and the "liferaft.lua" file) into it. I then copied an 'entry.lua' file from another Mod and modified it as needed, pointing to the Shapes and Textures folder, and the liferaft.lua fil. That made the life raft appear in the Ships drop down so I could place it but it doesn't get rendered Maybe I complicated it? I'll try just dropping the two folders and the liferaft.lua file into a folder of its own [EDIT] Just dropping the structure into a folder of its own, under ./Mods/tech doesn't make the life raft mod appear in the ships list

I did drop the zip's "Mod" folder into the Saved Games/DCS.openbeta (root) folder, yes. The result fro that is I get this structure for the mod: Saved Games/DCS.openbeta/Mods/tech/Textures/.. Saved Games/DCS.openbeta/Mods/tech/Shapes/.. Saved Games/DCS.openbeta/Mods/tech/liferaft.lua All other Mods have their own folder, with an entry.lua, usually also pointing to the equivalent of the liferaft.lua No, the historical filter is not active I tried creating a "Liferaft" folder, then moved the folder structure (./Shapes/*, ./Textures/* and the "liferaft.lua" file) into it. I then copied an 'entry.lua' file from another Mod and modified it as needed, pointing to the Shapes and Textures folder, and the liferaft.lua fil. That made the life raft appear in the Ships drop down so I could place it but it doesn't get rendered

Some more time has passed and I just found this. I tried using it as-is in 2.8 (beta) but it doesn't show up in the Ships groups list. I started b y just dropping the zipped 'Mods' folder into the open beta root folder but it doesn't seem to work. Comparing the Mods structure to what's already in there it's also very different, so I assumed the sim's Mods file structure has changed since this was created? Any tips for how I can make this work?

Duh! I just wasn't aware there's been a hot fix. I upgraded and that seems to have resolved the problem. Sorry for wasting your time!

Nope. I've had CA since release, full module.

I have had this error for two days now Seen it before, once or twice, but this time it seems it's not going away. Anyone else?

In the current multi threading preview version I can't seem to get a reliable handoff from TGP to the Mavs (D or H), despite having boresighted them. Process I follow for boresighting: Cold start as normal, then takeoff In air, go A-G and energize Mavs and TGP, then wait for them to be RDY Set TGP to AUTO and Mav WPN to PRE Set master ARM to SIM With TGP; find some high contrast target some 8+ nm out Acquire hight contrast target On Mav WPN format; align Mav crosshair with TGP target and lock. When crosshair collapses, press BSGT (and ensure it gets inverted on WPN format page) Select other Mav station and repeat items 6 and 7 With this done I move on with mission. But after fence in, a TGP target lock almost never get successfully handed off to MAV. I have tested this with both H and D versions with same result Has the process changed or is this just bugged in this version?

I recently experimented with the Portable TACAN. I wanted only range so I unticked the "BEARING" check box. The end result is I still get bearing but no range. Shouldn't it be the other way around?

Cheers! That was it!