Jump to content

Home Fries

Members
 View Profile  See their activity

  • Posts

    3515

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Home Fries

  1. Home Fries
    Adding to what Swordsman said, I recommend doing the 3-in-1 LOD last (when all of your other textures are complete. I actually keep a 3-in-1 template to make for easier updates as well when I update main textures. Finally, I recommend using Model Viewer 2 rather than viewing textures in game. This is better for checking those texture line-ups, zooming in, playing with light, and it loads a lot quicker. You can also update a texture and click "reload textures" to instantly see the change you made. Using Skatezilla's Launcher lets you launch Model Viewer 2 directly from the GUI. You may still need to use the game to see certain things (like the 3-in-1 LOD), but 99% of what you do can be done with MV2.
  2. Home Fries
    +1
  3. Home Fries
    OK thanks, @Hollywood_315 . I'll try without VSPX, though I really did enjoy not having to overannunciate everything :smilewink:. EDIT: Works fine now, thanks!
  4. Home Fries
    @Hollywood_315 I'm having issues with the Kneeboard extension. I just installed it and re-applied the voice commands in VoiceAttack to take advantage of the new "Kneeboard" command. When I would say "Kneeboard" it would usually not recognize the word or it would recognize "the board." I also exited out of VA and restarted VAICOM to see if that would fix it. No joy. Then I added the "Blue Brains" command phrase to the Kneeboard command and reapplied the commands to VA. Now VA would hear "blue brains" but the phrase is unrecognized. Compare that to "Scan Range 100," which works and demonstrates that VAICOM is working properly. As you can see from the first screenshot, I'm using the latest version of VAICOM, and VSPX is enabled. Any assistance is greatly appreciated.
  5. Home Fries
    I see no reason why not. VAICOM interfaces directly with DCS and not the module (exception: F-14 which is what AI RIO is for). VAICOM is mostly used for comms, which is straight DCS. I'll give it a try to be sure, though. You should be able to test it with free VAICOM. from the FAQ page EDIT: While the A-4 doesn't use radio comms, I just confirmed that VAICOM works with the ground crew interaction. I just used it to place/remove wheelchocks and rearm.
  6. Home Fries
    Sorry, I guess I'm dense, but I'm not seeing it on the downloads page of the website. OFC, I'm also not seeing the Realistic ATC extension either, which I know is released because I have it. EDIT: NVM, found it on the licenses page. :doh:
  7. Home Fries
    @Hollywood_315 I was reading the online PDF and saw the bit about the Kneeboard expansion on page 43. Any ETA on when this will be released?
  8. Home Fries
    I get the dialog box saying "Value cannot be null. Parameter name: path." Then it crashes.
  9. Home Fries
    Additional information: I created a F14 specific kneeboard location and that worked. It's the "All" kneeboard location that causes the crash.
  10. Home Fries
    I have FC3 and got the Su-33 standalone with the Supercarrier, but I have never installed the Su-33 standalone. I think there may be something else at work as well.
  11. Home Fries
    2.50c (Hotfix 3) is up. It fixes issues with the Mi-8, though the comms routine is still WIP.
  12. Home Fries
    Anyone? This is a fair question for skin developers.
  13. Home Fries
    Correct.
  14. Home Fries
    It's specific to the MFDs (3 buttons on the LMFD to match the 3 buttons on the left console in the jet). The flap switch is set for the 3 stage landing gear, as is my convention in similar Russian jets.
  15. Home Fries
    If you enable TriggerZoom on supported aircraft, you get this with trigger stage 1. Also, putting it on S1 will not remove it from substitute SnapViews. This also applies to Spyglass whenever possible. EDIT: here's an idea I may be able to implement for Warthog users. Currently, the Cougar landing gear/flaps are near-globally set to S3+H3U/D. This could be reserved for VR Zoom and Spyglass Zoom in lieu of any shifted functionality. I agree with you in principle, but the nature of the modified view means that holding the zoom (currently if you double-tap S1 you get zoom held in place) if shifted would continue to screw up the rest of the HOTAS mapping. To keep it simple and functional it needs to remain unshifted, which is why I chose S1. I originally put in the mouse commands on request by VR users. I get where you're coming from, and in the future I can put in a VR Trim = 2 option that sets the shifted Hat1 to be like TrackIR without padlock (e.g. rudder trim or station changes).
  16. Home Fries
    I've been running a trial balloon with S1 for a few aircraft and it seems to be working well. Default S1 functions very rarely require a lot of manipulation or sustained hold, so they tend to work well as S3+S1. This allows S1 to be used for VR Zoom. The functionality just seems to work well. Unshifted functionality makes it easier to keep the zoom on without compromising other HOTAS commands. Additionally, the thumb is still free, allowing you to use the mouse commands if you set VR Trim to 0. S3+H4 is not a "standard" I came up with; all I have been doing is replacing SnapViews with VR commands, whereas S1 should become a de facto standard. SnapViews will continue to be replaced by VR commands and Rudder Trim as required. Since I don't use VR, I depend on people who do. If you can give me a compelling reason to keep the views on S3+ a hat switch, I'm happy to consider it.
  17. Home Fries
    If you use VR, S1 should map to VR Zoom and S3+S1 does NWS.
  18. Home Fries
    I had no trouble with it. Please let me know what HOTAS you're using, your head-tracking (e.g. POV, TrackIR, VR), and if VR, whether you default hat1 to trim or mouse.
  19. Home Fries
    In 1.8.0.4, when I try to select a new Kneeboard location using profile selection, I get the dialog box saying Value cannot be null. Parameter name: path. I have run as administrator, I've tried replacing the files, and I can't clear the error regardless of which profile I select. Any ideas for a workaround? EDIT: Win 10 with DCS 2.5.6.55960
  20. Home Fries
    2.50 Hotfix 2 is now available via the CTS Updater.
  21. Home Fries
    And here's the latest text I put into the documentation:
  22. Home Fries
    Thanks for that. Doubling the FOV looks like a plan for forward/default views, and this is a good workaround for the specific views as well. I would love to include some "tweaked" specific views as well, e.g. zooming in to the left/right instrument panels to get a higher resolution view. For triggerzoom, it's actually a two-step process. First, when the logical gearstate is up (i.e. TARGET thinks the gear is retracted), press S3+TG1 to enable TriggerZoom. Then holding TG1 will cause the view to zoom in for as long as TG1 is held. S3+TG1 again disables TriggerZoom. Of course, you can always just use the FOV Zoom on the Warthog throttle friction knob to test the view as well.
  23. Home Fries
    Good to know. I don't understand what cockpit_version is for, but I can definitely update the values for the next version. Since I have 16:9, I can really only do SnapViews for 16:9. Is it fair to say that at least for boresight, the only thing that needs to be changed is FOV? If so, what is a good default FOV? Also, if you could provide 32:9 SnapViews I would put them in and give you credit.
  24. Home Fries
    Looks like I may have trimmed a bit too much from the tree. :doh: I've uploaded 2.50b alpha 2. Again, just extract to your CTS folder. If you haven't yet patched to 2.50a, be sure to do so first. EDIT: 2.50b now available via the CTS Updater.
  25. Home Fries
    No problem, thanks for the report. I'd rather get a report on something that works than not get a report on something that's bugged! :smilewink: I'll look at the idle issue. It may just need a longer pulse. I won't do anything about it until the stack issue is fixed, though.
×
×
  • Create New...