-
Posts
316 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Razi
-
I did have issues at first. I spent a while troubleshooting the code, but ultimately, somewhere along the way it just started working,so I've actually no idea why it started working unfortunately. But here is what I did anyways, if it helps. I scanned modded NATO.lua file in this mod and found the modified code in the MGRS function. Then started manually adding it, line by line, to an unmodified NATO.lua file, testing each time to see if VAICOM still works after each edit. I wanted to find the code that was stopping VAICOM from working, but VAICOM ended up working after every edit until I manually added all the modified code and it was still working... After it was all working, I modified the code so that only the Lat/Long coordinates are read, was just a personal prefence of mine.
-
Make sure that the options are set in the waypoint options, not the triggers tab. I made that mistake when I was first trying to set up a JTAC. Invisible and immortal will then work.
-
Thanks for this!
-
In the Hornet, TOT is set for only one waypoint (TGT) in a sequence. In other words you cannot set more than one waypoint as TGT. Also note that the REQD GS is calculated from the currently selected waypoint to the TGT in order to reach the TGT at the TOT.
-
Just tested it again and GSPD is still bugged though. See here: https://forums.eagle.ru/showthread.php?t=232012
-
I asked this question to a Hornet driver before. I've been told the following: 1. The CLIMB function shows “optimum climb speed". It was a best climb schedule speed. Basically an energy function climb. It follows the bingo charts in NATOPS, but uses your actual realtime weight. 2. MIL Power 3. No. ATC holds KTAS and the CLIMB function shows KCAS. In practice, ATC is generally used only in level flight where KTAS and KCAS remain the same.
-
Thanks guys, I got it to work! I actually didn't think to try a different port because FFB works great on all the modules that have it implemented. It ended up being my usb hub that seemed to be the issue. Though for my setup it is inconvienient to move the stick from the hub to a usb port on the motherboard, it did start to work. I tested it out and got simFFB working in DCS since and so I went ahead and bought the C-101! Excited to use it to learn flying fundamentals. I look forward to the full implementation of FFB, especially for the trim.
-
Thanks for the input Ramsay. At your suggestion I changed the preferred device for older programs to the MSFFB2, then tried to run simFFB without DCS to see if anything happens, but still nothing (also with administrative permissions). No FFB on the stick at all. I have a fresh install of Windows 10 Pro. I tried simFFB awhile ago with the other trainer I mentioned and at that time was running Win 7 Pro, but I also had no luck with it working then either and gave up. I only just recently completely rebuilt my computer and installed Windows 10, about 2 weeks ago. I'm testing everything I can think of including disconnecting other USB devices, shutting down background process, etc., still no luck.
-
That is what I thought should happen. No, if I open simFFB by itself, nothing else running, nothing happens, stick is limp. If I run a DCS mission first, then open it, still nothing changes. The default DCS FFB still runs, so the stick is limp with the Mustang on the ground in a cold start. I've tried running it as administrator as well. I haven't come across anyone else with this issue, so I'm at a loss. Honestly, if I can get simFFB to work I think I'd be willing to buy the C-101 and fly with it until you get around to implementing FFB.
-
Hrm. I can't figure it out. I read through the original thread, but nothing I try seems to have any effect. I launch it after I load a mission in DCS and have the MSFFB2 selected and nothing seems to happen, the settings don't do anything and the stick feels exactly the same. I alt-tab and select Init DirectInput and still nothing. I've tested it on a few aircraft and thought that if I tested it on the Mustang on the ground where the stick is limp, when simFFB overrides the FFB the stick should have a spring effect, but nothing happens. I assume the number beside the joystick menu in simFFB is the usb device? I've tried them all at any rate.
-
Thanks, though I've never gotten that tool to work. Tried it again with no success. (Windows 10, Microsoft SideWinder FFB 2)
-
Has this been implemented yet? (Sorry, I haven't been following the C-101 updates) I'm learning to fly with the help of a pilot friend and he advised me to practice TACAN instrument landings at Nellis. I've understood that this would be the aircraft to get, especially to practice in an analogue pit, for this purpose. Unfortunately, without FFB support, I just won't be able to fly it with my setup. I had a different trainer that I was hoping to eventually be able to use to practice this kind of thing with, however that developer told me they had no intention of supporting force feedback "ever", not even willing to implement a spring effect (which is all the Hornet currently has). Unfortunately I didn't realize it would be unflyable without any kind of FFB support until after I bought.
-
[FIXED] ADI Yaw Indicator not correct for Standard Rate Turn
Razi replied to Binary's topic in Bugs and Problems
I was learning how to fly a CASE III Marshal holding pattern today and first decided to test the Hornet's standard rate turn. So, I flew circles for awhile testing out the ADI and standby indicator for half standard and standard rate turns. Standard rate turns, with the boxes aligned didn't result in a 2 minute, 360 degree turn like you said. They ended up being about 45 seconds too fast. However, half standard rate turns seemed to work good with the box centered below the gap, resulting in a pretty precise 4 minute, 360 turn. So that at least worked well for the Marshal holding pattern that uses a half standard rate turn. Also, the ADI and standby boxes go in opposite directions. -
Would love to see an ingame mission/campaign manager that you can search for and download missions/campaigns with community created content as well as official (i.e., Wag's occasional free missions). Consolidating game content to an ingame area would be super convenient to find and download content. It may help promote newly released content as well. Firing up DCS and getting an alert that Wags posted another "Mission of the Week" and being able to download it and fly it in one or two clicks would be a welcome sight. As it is, there is content out there, but it is spread out all over the place. Personally speaking, having this kind of thing ingame would make DCS feel full of content that is ever expanding. (This is a wishlist forum, not a "is it practical?" forum. I'm not a developer, just a wish maker!)
-
[REPORTED] GSPD setting doesn't seem to work properly for TOT sequencing
Razi replied to Razi's topic in Bugs and Problems
Thanks Ramsay, that is what I've been experiencing. GSPD didn't seem to be changing the required GS at all. Wasn't sure if I was setting things up properly or not for GSPD to take effect. -
Unfortunately I didn't find any good tutorials. I only was able to find a post on its github issues tab that clued me into how to get it to work with on-off toggles. If I understand correctly, Joystick Gremlin remaps the joystick to a virtual joystick thereby allowing JG to customize the action of a given button press/depress. With the on-off toggles, you add a macro action with a recorded key press/depress. Then you add a condition to this action that when this virtual button (activated by the physical button) is pressed, the macro is run. For on-off toggles, you need to use two macros - one for "On" and one for "Off". Linked below are snips of my tail hook configuration (couldn't figure out how to embed them, sorry). Macros Conditions
-
It does. I use Joystick Gremlin for my On-Off toggles. You have to use macros though, and conditions with activation on the virtual buttons.
-
[REPORTED] GSPD setting doesn't seem to work properly for TOT sequencing
Razi replied to Razi's topic in Bugs and Problems
Still no success for me setting GSPD. I added a third leg which made the flight plan about 3 minutes longer. I configured the TOT sequence during the first leg for a TOT of 16:10:00 (10 minutes) to TGT (waypoint 3). Then I flew the required GSPD of 322 kts the rest of leg 1 and all of leg 2. At the start of the third leg I flew the 450 kts I set and arrived at the TGT 48 seconds early. So I don't know if I'm not doing this correctly or if my flight plan is not setup properly. I have tried to make the parameters as simple as possible. Attached is this second test. TOT gdsd test 02.trk -
[REPORTED] GSPD setting doesn't seem to work properly for TOT sequencing
Razi replied to Razi's topic in Bugs and Problems
Thanks Ramsay, I'll do some more testing. Probably need at minimum a 3 leg sequence to properly test with. -
(Originally posted this is the wrong bug forum, sorry) I haven't been able to get the GSPD setting to work in TOT sequencing. I set up a simple 2-leg flight with each leg being about 20nm. At 350 GS it takes ~7 (6:53 in the mission editor) minutes to fly. I then experimented setting up different TOT for waypoint 2. It works perfectly if I set only TOT and fly the required GS. I hit the TOT at the TGT waypoint 2 spot on every time as long as my TOT is within the performance parameters of the aircraft. However, if I set a ground speed, things don't work. For instance, I set a ground speed of 400 GS and it required me to fly about 339 GS to waypoint 1 and then the 400 GS to the TGT at waypoint 2, but I arrive 32 seconds early. I've attached a track of this test. TOT gdsd test.trk
-
Will do! I just wanted confirmed with former Hornet pilot first and he confirmed this is supposed to be the behavior. So it seems GSPD is bugged.
-
I haven't been able to get the ground speed setting to work as has been described above, or I don't understand it still. I set up a simple 2-leg flight with each leg being about 20nm. At 350 GS it takes ~7 (6:53 in the mission editor) minutes to fly. I then experimented setting up different TOT for waypoint 2. It works perfectly if I set only TOT and fly the required GS. I hit the TOT at the TGT waypoint 2 spot on every time as long as my TOT is within the performance parameters of the aircraft. However, if I set a ground speed, things don't work. For instance, I set a ground speed of 400 GS and it required me to fly about 339 GS to waypoint 1 and then the 400 GS to the TGT at waypoint 2, but I arrive 32 seconds early. I've attached a track of this test.
-
I'm finding that I can spot targets up to 8nm away in VR - if I know where to look. Also, for the first time, I've noticed that I can actually see bombs as they are falling, which I never used to be able to see.