-
Posts
184 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by zippoa
-
That's because Earth is flat in DCS!
-
In game F/A-18 can take off from grass. It can't to that in real life due to pressure on soil.
-
And how to tell Jester to TWS only one of targets with multiple missiles? I mean, what commands should I click
-
There is command "STT lock" -> "Choose specific target" for Jester. There we get circle of possible targets with it''s range and azimuth. But in combat with many contacts it cant be quite hard to guess what contact is on what distance. Is possible to rework that part, may be add some numbers to contacts on pilot screen, so when I press "Choose specific target", in addition I also see number under range and azimuth. Like, "Contact 5, az 54*, distance 31 nm" Another though is if it is possible with Jester to attack in TWS only specific target, without switching to other after missile launch. And one more, what about new option "TWS specific target" or "TWS enemy target ahead" Thanks!
-
Sometimes it takes too long in RWS mode to IFF contacts
-
I think you should be able to turn on/off mirrors by clicking on them like in f-18
-
Thanks! Daaaamn, so I lost 3000 every time
-
Jester just randomly suggest to drop tanks. When I press A button to call jester menu, there appears circle with two options "Spot" and "Jettison fuel tanks". All this happens when I am in A/A mode. Sometimes this menu appears just after take off with full fuel tanks. And most annoying that this menu repeats from time to time. Even if fuel tanks are already dropped, this menu appears again with option to drop tanks. Dropping jettison tanks under WVR is good. When I see that total fuel is 16000, I enter that menu and tell Jester to drop tanks.
-
DON'T show menu to drop fuel tanks at first invocation! Leave where it is now -> Within visual range - > Jettison tanks. I was just killed because enemy appeared close and when I called menu to change radar range, that menu appeared and my usual button clicks were ****ed up due to other order of menu
-
When flying for long time on one vessel with multiple landings, INS starts to drift. This can be seen by doubling radar contacts (Two contacts near each other instead of one) My human RIO was able to re-calibrate to remove this drift. I think Jester should be able to do it too
-
There are bindings in controls: "Switch between PSTT and PDSTT" and "Break lock". Could you add all possible bindings to pilot controls. No need to bind to specific key, I would bind it to joystick. My most useful are: 1) Radar distance: "25 nm", "50 nm"..."400 nm" 2) STT target ahead 3) STT enemy ahead 4) Radar modes: TWS/RWS/auto 5) Go radar silent 6) Enable radar Also, it possible to add commands to Jester to control radar elevation smoothly? Like commands: "Radar 10 degrees up" and "Radar 10 degrees down". And also bind them. So add some more options to existing "Middle low", "Low"...
-
Multi-monitor set-up guide & help (unofficial)
zippoa replied to MadTommy's topic in Multi-Display Bugs
For you it should be this _ = function(p) return p; end; name = _('MY_MFCD'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920 / 1080; } } LEFT_MFCD = { x = 2086; y = 470; width = 700; height = 700; } RIGHT_MFCD = { x = 3110; y = 470; width = 700; height = 700; } F14_HSD = { x = 2086; y = 470; width = 700; height = 700; } F14_VDI= { x = 3110; y = 470; width = 700; height = 700; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center --LEFT_MFCD = Viewports.LEFT_MFCD --RIGHT_MFCD = Viewports.RIGHT_MFCD -
Multi-monitor set-up guide & help (unofficial)
zippoa replied to MadTommy's topic in Multi-Display Bugs
Also man, your settings are totally incorrect _ = function(p) return p; end; name = _('HSBMFD1'); Description = '1 Screen and L-R MultiMFD' Viewports = { Center = { x = 0; y = 0; width = 3968; height = 1080; viewDx = 0; viewDy = 0; aspect = 3.7; }, LEFT_MFCD = { x = 1920; y = 0; width = 525; height = 525; }, RIGHT_MFCD = { x = 3443; y = 0; width = 525; height = 525; }, } UIMainView = Viewports.Center LEFT_MFCD = Viewports.LEFT_MFCD RIGHT_MFCD = Viewports.RIGHT_MFCD Here you say DCS that your mains screen has resolution 3968*1080. But yours must be 1920*1080 -
Multi-monitor set-up guide & help (unofficial)
zippoa replied to MadTommy's topic in Multi-Display Bugs
Here is how it works on my PC. I have 1920*1200 + 1024*768 + 1024*768. Two small monitors in Windows setup are located right in bottom in one line from main monitor _ = function(p) return p; end; name = _('MY_MFCD'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1200; viewDx = 0; viewDy = 0; aspect = 1920 / 1200; } } LEFT_MFCD = { x = 2086; y = 470; width = 700; height = 700; } RIGHT_MFCD = { x = 3110; y = 470; width = 700; height = 700; } F14_HSD = { x = 2086; y = 470; width = 700; height = 700; } F14_VDI= { x = 3110; y = 470; width = 700; height = 700; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center --LEFT_MFCD = Viewports.LEFT_MFCD --RIGHT_MFCD = Viewports.RIGHT_MFCD In options menu in DCS choose resolution 3968*1200. It should be last in list. Also choose aspect ratio about 3.3333 In your case, you should only change vertical resolution 1200 to 1080. When my DCS loads, image is squeezed on center screen, so I press Alt+Enter or just click with mouse on my mfcd and image goes normal -
Move cargo/sling indicator to center screen With multiple monitors, this indicator that is usually top-right position moves to most right monitor
-
Suggest also to add "spot circle" like we have for SAM units or artillery. This way for tac commanders it will be easier to understand what radius covers JTAC
-
We need some slider for SAM like "intensity" maybe. Right now what we see in multiplayer: enemy F/A-18 get high to launch their JSOWs. Our's S-300 site with 6 launchers sees them far away and starts to shoot. It is shooting missiles like from machine gun, missile after missile. And all missiles on one target! Enemy jets make some smooth and launch JSOWs, turn away and are safe. Now our S-300 site has empty launchers and rearming, JSOWs will glide and destroy targets. S-300 under AI control should change behavior and launch for example 2 missiles per each target and wait to check if it misses or hits target. No reason to launch all missiles at one target simultaneously. Another suggestion is to add for TOR checkbox to disable engaging enemy jets, and engage only missiles like JSOW/Mawerick. Right now clever pilots drain TOR's missiles and only after launch Mawerick