Kaitsu
-
Posts
89 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Kaitsu
-
-
It does not.
-
Is this broken now? I set the LGB code to 1686 on mission editor and 1686 on TGP and bombs won't guide to the lased target.
-
Looks only on road and off road formation type groups disperse under fire. If type is set to e.g. line abreast the group will not stop and disperse but push forward. On the attached mission F16 hit three groups and the southern most group does not disperse. Not sure if it is a bug or not but I believe it is not documented anywhere at least.
-
I tried adding two JTACs and a SA-3 where Low Blow radar is 'hpriority' and the other units in SA-3 group are just regular units. Then there are couple of 'priority' units. For some reason JTACs started to lase SA-3 regular (launchers etc.) units before 'priority' units after 'hprioriry' unit is destroyed.
-
On 9/6/2020 at 7:33 PM, Yuriks said:
I can not move past first training flight with F5. After it ends for whatever reason, there is a command "recycle India".
I circle it forever but the next training flight, with F-16, does not start.
Any advice?
I also tried this and have the same problem.
-
The problem is that no matter what the last boolean is the group will always head to the closest road and not straight to randomized point on the map.
Edit: I was actually using groupToRandomZone. Anyway group will always head to the closest road. Mission file attached. -
I think I was wrong and it works as advertised after all. So if roadUsing is false the group will still always use the roads if it is far enough from the arrival zone. I was trying to create a mission where group will head straight through the desert to a random point/zone. Is it possible to do with MIST?
roadUsing = boolean. If false and the group is 1.3 * radius outside the center of the zone, the group will go to the nearest road and follow it to the nearest on road point of the new random point in the zone. -
Why is it that mist.groupToPoint useRoads parameter needs to be true for group to NOT use roads and vice versa?
-
Hi. Do you have a driving wheel connected to your PC? If so, try unplugging it.
Otherwise please atach your dcs.log file.
Wow, it was crashing on start for me and even the fresh install / deleting Saved Games folder did not help. But looks unpluggin the racing wheel helps! Here is the log with racing wheel attached.
-
crashes every start up, crash report sent
[update: I removed my usb wheel and my second usb keyboard, now it starts up fine again. Had never a problem with older dcs versions. Perhaps the way controllers are handled changed.]
Also crash on every startup. Tried your tip unpluggin USB racing wheel and it helped! However if I plug it back it crashes on start again.
-
I forgot to spend my expiring $26 bonus. :(
Why you could only use $3 out of $10?..
-
Well actually noticed now that Flap+mic forward does not simply work for any mapping.
-
I have got a strange problem. I am using joystick pinky flap as a modifier and have mapped A-10C mic switch radios as flap modifier with throttle mic switch. All the other directions work but mic fwd does not. There is no VHF AM menu or mic switch animation in the cockpit. Tested it with keyboard modifier LCtrl and it worked just fine. Flap+mic fwd mapping has been working for years for me.
-
Seems to be working in internal version. I'll ask to check anybody from ED team.
OK, we checked in public beta.
Radio is functioning.
Maybe it would help:
1. Selecting simple radio in game setup.
2. Using not " \ " but " RAlt + \ " for communication via currently selected radio.
Simple radio seems to work, thanks.
-
Same here!As posted above, I have had this Crash on Exit from the game for almost a year in the Stock, Beta, and Alpha versions.With this last update it seems to have been fixed. I've waited a few days for testing because I didn't believe it. But it does seem to be fixed. Not sure if the game was fixed, or an update on some software(AV/FW) or the big (April) Windows Update that was installed the day before the DCS update or what.. But it's not crashing on exit finally..
Sent from my SM-G965F using Tapatalk
-
I have had crash on exit for months as well with all the versions. I am not using Steam version.
-
Does it appear in other missions/modules? Or just in that particular mission and campaign?
Never happened to me in any other mission or campaign ever. Does it work for you?
-
The problem is that general radio menu does not open. The only way to get general radio menu back is to land at the home base.
-
Crash on exit for me as well.
-
For some reason radio menu won't open at Vladikavzak when I asked to report. When I fly back to base the radio menu is enabled again.
Edit: Looks radio menu gets disabled right after I take off and I get it back when I land. Anyone else has the same problem?
-
I have a problem on the 2nd mission when entering the valley. Radio menu does not open to access F10 menu to report in... For startup and take off the radio menu works just fine.
Edit: Looks that if I get back to the base the radio menu is enabled again so I reported in and flew to canyon but got route deviation message and was thrown out... :o
-
Last night tried this with a friend of mine with DCS World 1.5 beta. First we used the default laser code 1688 and everything worked fine. Then changed mine to 1687 on my TGP and lased a target for him. He was still able to find my lased target with LSS using code 1688 and his LGBs destroyed the target. He was not lasing himself and his bombs were set to default 1688 also. Is the laser code modelled correctly in 1.5?
-
Very good idea!
-
1
-
-
They need to be in a same group. The easiest way to do is to add couple of launchers (LN) and then change one of the launchers to radar (STR). Some SAMs like SA-11 need also a command vehicle (CC).
Ramat David ILS
in DCS: Syria Map
Posted · Edited by Kaitsu
It works for you with 111.10? I get an vertical bar some miles before the runway but the it suddenly disappears... I tried it with a10 and f16 and have done this million times with other ILS runways.
Edit: Looks I just did not have enough headwind on the mission...
6 kts headwind is not enough, need 8...