Jump to content

Home Fries

Members
  • Posts

    3515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Home Fries

  1. It should still work, but I'll fix this for next release. Thanks for the report. :thumbup:
  2. See Appendix E in the Advanced Configuration Guide. :thumbup:
  3. That's my point. If the radar updates the target position, any error in the present position (Bk90 starting point) will be negated by the same error in the destination coordinates. The relative accuracy should be limited only by the accuracy of the radar fix.
  4. Assuming you're using the Warthog throttle, I already use the 3 position switch logic, so that's entirely on ED/RAZBAM. I recommend releasing to center for a quick pulse prior to going to the opposite button, so DCS recognizes that one switch is released before the other one is activated.
  5. I'm not sure I understand this. If the Bk90 is inertially guided (i.e. not from an external source like GPS), then any error in the nav computer should be offset in the Bk90 provided the target position is updated using the radar. Bottom line: the relative accuracy from the aircraft and the updated target position should only be due to the accuracy of the radar fix. If you leave the target waypoint as is, then your statement makes a lot more sense.
  6. If 11 along with 31 and 32 are displaying in Joystick Analyzer, the profile is working. Adding it to DCS Options is sometimes tricky. You may need to map the desired button or switch, then manually add the modifiers to match.
  7. Thanks for the report. When I added AWACS Mode I forgot to resequence the selection arrays. Fixed and the 2.29a hotfix is now up. EDIT: FYI, there is no customary change of the change log or database increment for this update. I am too far along on 2.30 to revert either in order to document the hotfix. However, the hotfix is noted in the Updater log, so if you see the script as 2.291 you know you have the hotfix.
  8. Set DX30, DX31, and DX32 as modifiers for the Yak and CEII. Then the throttle buttons should register properly.
  9. The skins are in the Mods\Aircraft\C-101\Liveries folder, when they should be in the CoreMods\Aircraft\C-101\Liveries folder. That's why you need the module to see them. This is something that should be easily fixed by AvioDev.
  10. Now that MV1 is officially toast, is there any ETA on the fix for MV2? Or would ED consider bringing back MV1 as a stopgap until MV2 is fixed?
  11. Right now you need to double-tap Hat1 to cycle the control mappings, even though a single tap will change your station. I'm updating this for the next build.
  12. I will look into this. The POV hat cycles the active station in the Mi-8 (and almost any multi-seat aircraft for that matter). H1L is the pilot, H1R is the copilot, S3+H1L is the door gunner and S3+H1R is the flight engineer. In the logic, Station 1 is the right seat (i put this code in originally for the Huey), station 2 is the left seat, and 3+ are for other stations. Thanks for the compliment!
  13. Version 2.5.41 is up. It supports the DCS 2.2.4.27430 hotfix.
  14. I like a combination of these ideas, selectable in the mission editor. Lights On 1 hour before/after dark (default) Lights Off Selectable with F10 (from within coalition) Also, if option 3 is selected, being able to toggle this from the F10 View (not just the comm menu) would be awesome.
  15. You can do this already, but the music has to be built into the mission. Convert your music file to ogg format, then in the ME set your trigger to Play Sound (and select the music file). Just fair warning that if you do this for a multiplayer mission, the resultant size of the mission is likely to make for long client load times.
  16. Version 2.5.40 is up. It's compatible with 2.5.4.27314 (i.e. Openbeta at the time of this post) and fixes an issue with the UK only mod.
  17. Version 2.29 is up. 2.29 Adds AWACS Mode, makes various AV-8B improvements, and fixes some bugs. Additionally, 2.29 allows you to launch MFDisplay from within the script, so whenever you load a profile you get the appropriate MFD graphics on an auxiliary monitor. The FC3 and AJS37 bugfixes were also retroactively applied to the 1.5.8 Legacy version of CTS.
  18. Thanks for the compliment! Found and fixed for next release. This is actually by design. Set Left throttle as analog throttle = 1 in CTS for either/both the UH-1 and SA342 to get helicopter > 1. Otherwise a digital throttle is used.
  19. I was actually trying it with the Harrier when I put a skin in coremods, so I’ll try another model. Problem is with the new pilot model/texture for the Harrier pilot I need the Harrier to work. :mad:
  20. Thank you for this observation. Concur. This is what I meant, but you were more articulate in your description. I really want to see this squared away. At this point, I can't even put my own skins in the DCS World liveries folders without seeing everything show up as the green digicamo of the missing texture. :cry:
  21. No other way right now. I'm looking into a way to do it with HOTAS only for VR users, but this likely won't happen until spring.
  22. I'm still having trouble getting this to work, despite having created symbolic links. Here's my setup: My DCS World installs are on the G drive (G:\DCS World OpenBeta for this example) I set up a folder on G called MV2_Path, where I put DCS.Openbeta. In DCS.Openbeta I created symlinks to the liveries and textures folders in my original Saved Games\DCS.Openbeta folder. They map to: G:\MV2_Path\Textures (I use a shared texture folder across all DCS installs) G:\MV2_Path\DCS.Openbeta\Liveries Here's what I added to the autoexec in Saved Games\edModelViewer2.openbeta\autoexec.lua: scan_for_textures("../../MV2_Path/DCS/Textures/") mount_vfs_liveries_path("../../MV2_Path/DCS.openbeta/Liveries/") I can now see two folder names for each type of aircraft (one for each livery folder), but the contents of each folder show the liveries in the original DCS World install. For example, I see two AV8BNA folders in the livery viewer dialog, but both AV8BNA folders have only the skins that come with DCS (not my custom skins). I have also removed the trailing slash in the paths and get the same results. Any advice is greatly appreciated.
  23. Thanks for the great reply, Captain Orso. I keep DCS on a SSD separate from my operating system, so I fall into the category you described last. I'll see what I can do with system variables to make it work.
  24. A vote for the M2000C and a clarification. The M2000C does have TWS mode, but since it’s only Fox1 capable it needs STT to engage BVR. What you’re thinking of is the ground radar. RAZBAM is waiting for ED to implement ground radar in the Hornet, then planning to port the tech to the M2000. So they’re not “giving up” on the module. I think it’s a lot of fun to fly.
×
×
  • Create New...