-Ice
-
Posts
462 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by -Ice
-
-
Lol, beg your pardon then, but like I said, I tried it with that option ticked and un-ticked, didn't work.
In fact, I just tried this again. I started up DCS World, went to Options, UN-TICKED the Disable Aero box, clicked Ok, then exited the sim. Went to Notepad++ to confirm that keepComposition=1 is still active, saved the SoftTHconfig file, then started up DCS World again. I went to Options a second time, just to confirm that the Disable Aero box is still UN-TICKED, then launched a mission.
Helios gauges still do not display on #1 screen.
-
Okay, here's another obstacle. I have SoftTH running exactly how I want it now, but I can't get Helios to appear on my lower monitor (#1) when DCS is running.
This is my SoftTH config:
[main]
renderResolution=4480x2160
nonlocalFormat=RGB16D
keepComposition=1
smoothing=1
debugD3D=0
zClear=0
vsync=0
tripleBuffer=0
screenshotFormat=jpg
dllPathD3D9=auto
dllPathDXGI=auto
dllPathD3D11=auto
[overrides]
forceResolution=0
antialiasing=0
processAffinity=0
FOVForceHorizontal=0
FOVForceVertical=0
[debug]
compatibleIB=0
compatibleTex=0
compatibleVB=0
enableVBQuirk=1
[head_primary]
sourceRect=1280,0,1920,1080
screenMode=1920x1080
[head_1]
; Autodetected as \\.\DISPLAY1 at AMD Radeon HD 6900 Series
devID=1
sourceRect=1280,1080,1920,1080
transportResolution=1920x1080
transportMethod=auto
noSync=0
fpsLimit=0
[head_2]
; Autodetected as \\.\DISPLAY2 at AMD Radeon HD 6900 Series
devID=2
sourceRect=3200,0,1280,1024
transportResolution=1280x1024
transportMethod=auto
noSync=0
fpsLimit=0
[head_3]
; Autodetected as \\.\DISPLAY4 at AMD Radeon HD 6900 Series
devID=3
sourceRect=0,0,1280,1024
transportResolution=1280x1024
transportMethod=auto
noSync=0
fpsLimit=0
As you can see, I have incorporated your suggestions keepComposition=1, zClear=0, enableVBQuirk=1.
This is how my settings look in-game:
I've tried playing with both Disable Aero Interface ticked and un-ticked, still can't see my Helios gauges.
Did I miss anything? It's 1am here so I must've. Any help appreciated.
And yes, this is the first time I got a multi-monitor setup and this is the first time I am experiencing DCS A10C with triple-screen for views and a dedicated screen for instruments and MFDs so it is very exciting!
-
Ah, thanks for the help then! I got all 3 monitors working now, in Fullscreen mode, with each of the side-monitors being offset a bit ending up giving me a panoramic-arc view of the battlefield. Very nice in-cockpit but makes for interesting effects when watching weapons go in.
This is my 4-screen .lua setup:
_ = function(p) return p; end;
name = _('4 Monitors 2 MFCDs');
Description = '3 Monitors, 2 MFCDs on the upper left and right corners of the 2nd screen';
Viewports =
{
Left =
{
x = 0;
y = 0;
width = 1280;
height = 1024;
viewDx = -1;
viewDy = 0;
aspect = 1.25;
},
Center =
{
x = 1280;
y = 0;
width = 1920;
height = 1080;
viewDx = 0;
viewDy = 0;
aspect = 1.777777777777778;
},
Right =
{
x = 3200;
y = 0;
width = 1280;
height = 1024;
viewDx = 1;
viewDy = 0;
aspect = 1.25;
}
}
LEFT_MFCD =
{
x = 1280 - 00;
y = 2160 - 440;
width = 440;
height = 440;
}
RIGHT_MFCD =
{
x = 3200 - 440;
y = 2160 - 440;
width = 440;
height = 440;
}
UIMainView = Viewports.Center
Is there anything wrong with it or anything I can "optimize" a bit? I'm running SoftTH with all 4 monitors included, with #3, #4, and #2 showing the cockpit and #1 showing the MFDs.
I get a weird effect when using Helios and this setup, namely when I switch to Mavericks nothing comes up in the MFD and the ocean starts "blinking" on and off... hmmm... now to investigate how to make Helios run properly.
Sorry for the confusion regarding the iPad... it won't show anything as part of the cockpit tied to SoftTH, but I will simply be using this like an iPadPit to send commands to the sim rather than having to use the mouse.
-
A quick test with SoftTH and a 4480x1080 res in DCS with Fullscreen mode using the 1Camera.lua was a success!
Now to test a 3Camera.lua modified setting to see if I can get it to work.
-
BTW, this is how my setup looks like from the SoftTH config tool:
-
Hello PeterP and thanks for dropping by.
This is how my monitors are arranged. #2 and #3 are the 19" 1280x1024 ones, #4 is the "main display" 24" 1920x1080, and #1 is the 22" 1920x1080 which I will use to display MFDs, gauges, Helios, etc.
I want #3, #4, and #2 to display the cockpit view and #1 will simply be black background and Helios and exported MFDs on it. My CDU and UFC will be on my iPad :thumbup:
The upper-left corner of #4 is 0,0 so the upper left corner of #3 is -1280,0. I've had a quick re-read of your "MonitorSetul.lua"1.0.2.pdf and if I've missed any info you require, please tell me.
So, a couple of straight questions:
1. It is not possible to play multi-monitor config in Fullscreen mode (except for SoftTH), correct?
2. Fullscreen is only possible with SoftTH?
3. Will I need to enable all 4 monitors/heads on SoftTH, or just the #3, #4, and #2 monitors?
I've not played with SoftTH on DCS yet but I am using it with Falcon 4 BMS... I was simply hoping there was a solution without SoftTH but if you tell me now there isn't then I'll stop testing and just use SoftTH.
Thanks!
-
Ace, I have read Peter's help guide but could not find what I needed. Either that or I've not recognized it.
So is there no way to do this aside from SoftTH? Still, SoftTH is easy enough to do...
-
I'm trying to get DCS A10C to work with my setup but so far it keeps crashing between the GUI screen and the loading screen.
My setup is 4 monitors, two 19" 1280x1024 monitors for left and right screens, a center 24" 1920x1080 monitor, and a bottom 22" 1920x1080 monitor which I intend for gauges and MFD display.
So far, any attempt at extending the display across more than one monitor results in a crash. This is on a clean install of DCS World and DCS A10C 1.2.0.
I have tried editing my .lua files. Here is my attempt at just getting the top and bottom monitors (24" and 22") with the cockpit on the top monitor and the MFDs on the bottom:
_ = function(p) return p; end;
name = _('IceTest2 Monitor 2 MFCDs');
Description = '1 Monitor 2 MFCDs on the upper left and right corners of the 2nd screen';
Viewports =
{
Center =
{
x = 0;
y = 0;
width = 1920;
height = 2160;
viewDx = 0;
viewDy = 0;
aspect = 0.8888888889;
}
}
LEFT_MFCD =
{
x = -10;
y = 1080;
width = 400;
height = 400;
}
RIGHT_MFCD =
{
x = 1920 - 390;
y = 1080;
width = 400;
height = 400;
}
UIMainView = Viewports.Center
When the in-game Monitor res is set to 1920x2160, it will only work if Fullscreen is off, putting Fullscreen on crashes DCS. With Fullscreen off, the entire cockpit is stretched across both screens; I only want it on the top screen. Plus the Windows taskbar is annoyingly present as well.
Changing the height = 1080 and aspect = 1.777777777777778 in the .lua file but keeping the in-game Monitor res at 1920x2160 puts the cockpit view on the top screen and the MFDs on the bottom screen, but the Windows taskbar is still present.
Any way I can get rid of the Windows taskbar? Is it possible to play with multiple monitors with Fullscreen on?
Off to work now, but will experiment with stretching the cockpit view across the top 3 screens later on.
-
Is that mission working with current version?
-
Thanks guys!
-
Thanks!
-
Is this going to move to pay-to-play? I've seen a link on the Pay section...
-
I am looking for a mission with which I can do FPS tests for various video card settings and in-game video settings. I tried to get StrongHarm's FPShell.miz files but it won't load in the game (fair 'nuff, it was an old mission).
Does anyone have one I could try?
Thanks!
-
Thanks guys! I think I'm missing something for JTAC. I got enemies and I got troops in close vicinity, but there is no JTAC option once I fly the test mission. Do I have to do something to assign a JTAC a frequency or some such?
-
I was wondering if it were possible to set it up so that the JTAC always gives a "Type 1 in effect" scenario? What do I need to do to get this?
-
In line with my VAC thread, I was mucking around in the controls section when I saw a couple of commands:
Switch Dialog - LShift+\
Switch to Main Menu - LCTRL+\
Comms Menu - \
Now, the comms menu command is familiar, but when I fired up the sim and tried the switch dialog and switch to main menu, nothing happened. Has anyone tried this before, or at least know what they do?
-
Hey guys! I'm trying to create my own profile for VAC to control radio comms but at the minute, it seems like the radio comm is very confusing. For example, if you contact ATC and call inbound, all subsequent choices start off from the ATC sub-menu. However, if you press any of the other Mic switches (UHF, VHF FM), then go back to VHF AM, you have to start over from the main menu.
To illustrate, if you were flying inbound and call in, it would be VHF AM -> (F5) ATC -> (F1, assuming it is the top/closest tower) Bantumi -> (F1) Inbound. Subsequent choices would be F1 - Abort Inbound and F2 - Request Azimuth. However, if you select UHF or VHF FM, then come back to VHF AM, you will have to select (F5) ATC again to get access to the Abort and Azimuth radio calls. Also, once you are near the runway and told to contact tower, the selection now is F1 - Request Landing, F2 - Abort Inbound, and F3 - Request Azimuth.
The same applies for other radio sub-menus, in that you'll stay on them if you key the correct mic, but will have to go through the main radio menu if you click a different mic.
Any help around this?
-
1. Every mission in the first campaign (only campaign I've seen) starts me off with nosewheel steering sharply to the left, or veering off to some direction until I hit the wheel brakes or adjust the nosewheel. Since all missions always seem to start me off with throttles at 100% on the runway, this means every mission becomes a dash to readjust. Kind of annoying. Is this a known issue?
For me, the jet does tend to drift to the right a bit, so during my takeoff roll, I need to use a tiny bit of left rudder to steer the nose wheel. I disengage the nosewheel steering at about 60knots as the rudder can now control the aircraft. The mission should NOT start you off at 100% throttles, unless your warthog is at full throttle and you have "Sync cockpit controls wit hotas controls" option ticked... so I suggest you un-tick it.
2. How normal is it to rely *heavily* on wingman or JTAC spotting for you? I have an ugly tendency to feel like I should be pulling more spotting weight myself, and end up searching for way too long.IMHO the AI wingman spotting is useless anyway since unless you're really quick, you can't get a tally on the target anyway. Plus they see things up to 10nm off. JTAC is a bit better.
3. When pulling into a turn, an alert goes off, first rapid beeping, then a solid tone the tighter the turn gets. I understand this means I'm bleeding speed/energy, but is this "bad" in all cases? When I'm landing I use this to slow down before my approach..That is you stall horn warning. IIRC the chopped tone is when you are 2 AoA units away from stall, and the steady tone is when you are 1 AoA unit away from stall. Or might be the other way around.
4. What's the extent of the A-10's maneuverability really? I'm sort of battling the plane trying to do things like split S'es, and I don't know if that's just me being a bit shit or if the plane isn't supposed to be doing them.The aircraft is very slow/sluggish when fully loaded or even with external ordnance. Try your tricks on a 25% fuel, no external load setup.
5. Are there any tricks to setting up a steady orbit of an area to keep it in constant view of the TGP when I'm trying to do some sort of FAC? I can never seem to get this right...Use the ALT autopilot. More bank angle means tighter turns so your TGP is masked for shorter time, but also means your view window is a bit smaller. Less bank means more view time, but also longer masked periods. Higher altitude is better too.
6. I'm very TAD dependent for situational awareness, and during JTAC I pretty much require the digital to know where to go. But I still don't know exactly what positions called out to me actually mean. So for instance when I hear "bulls 080 for 100", what does that actually *mean*? haha. Or 'Magic, BRA, 279 for 110, 7000, hot'. This stuff confuses the bejebus out of me.You can make a mark point using those information. Go to the OFFSET page of the CDU and input the bull radial (80) and the distance (100) and it'll put a mark point on that location, slave TGP to that SPI and search for targets!
on the topic.And as GG said, the manual is your friend. Peruse it at your leisure, but I hope my post has helped.
-
nemesis, what I wonder is if there is a message/radio call to say that mission is complete? Or do you just RTB once the ground assets make it to the final destination?
Also, I've noticed in mission 3 or 4, there are now two JTACs.... and neither one gives you the target set in your briefing. What I did was input the coordinates and took them out, and then cleared out what the two JTACs have to me as targets.
-
Hmmm... I've started in Beta 3 and unless I'm mistaken, the startup procedure is still more-or-less the same except for the EGI toggle on the NMSP panel...
-
Very nice work. Is it still random on airfields or can we set what we want?
Also, while I love the new runways, can I get more landing marks please?
-
PM sent.
-
1) Unlock the maximum string length:
within ...Games\DCS A-10C\Scripts\UI\CommandMenu.lua, search for and change local menuItemMaxLength from 26 to 100; this is the cutoff length where it uses (...)
Can't seem to find the menuItemMaxLength bit now. Any help?
-
I know we can make vehicles/aircraft "appear" by delaying their spawn time during missions, but is it possible to make them "disappear" later in the mission?
I know some assets like aircraft can land, taxi, and park and they are gone, but I'm thinking more of just terminating them in mid-air rather than congest an airbase.
4 monitor setup help!
in PC Hardware and Related Software
Posted
Helios is running fine and I am running the latest version (1.2.176); I re-checked Gadroc's website to confirm this. I am also using the latest version of DCS World (1.2).
I wasn't using an Aero theme, turned it on and now Helios shows up over my #1 monitor. "Showing up" and "actually working" are two different things though. I've probably tested 10x now and it worked only 2x! I've never had Helios crash this consistently!
SoftTH config:
[main]
renderResolution=4480x2160
nonlocalFormat=RGB16D
keepComposition=1
smoothing=1
debugD3D=0
zClear=0
vsync=0
tripleBuffer=0
screenshotFormat=jpg
dllPathD3D9=auto
dllPathDXGI=auto
dllPathD3D11=auto
[overrides]
forceResolution=0
antialiasing=0
processAffinity=0
FOVForceHorizontal=0
FOVForceVertical=0
[debug]
compatibleIB=0
compatibleTex=0
compatibleVB=0
enableVBQuirk=1
[head_primary]
sourceRect=1280,0,1920,1080
screenMode=1920x1080
[head_1]
; Autodetected as \\.\DISPLAY1 at AMD Radeon HD 6900 Series
devID=1
sourceRect=1280,1080,1920,1080
transportResolution=1920x1080
transportMethod=auto
noSync=0
fpsLimit=0
[head_2]
; Autodetected as \\.\DISPLAY2 at AMD Radeon HD 6900 Series
devID=2
sourceRect=3200,0,1280,1024
transportResolution=1280x1024
transportMethod=auto
noSync=0
fpsLimit=0
[head_3]
; Autodetected as \\.\DISPLAY4 at AMD Radeon HD 6900 Series
devID=3
sourceRect=0,0,1280,1024
transportResolution=1280x1024
transportMethod=auto
noSync=0
fpsLimit=0