zaelu

Sometimes in battle you are overwhelmed. Some chose to stay safe in those times some accept the challenge (I'm not talking about myself... I''m struggling to find time to play). But, if the rounds until now were won in a balance kind of way... maybe more by red... maybe we should play along and have a bit of trust in devs. I play always red by the way and this 8th rounds is the most I like. SRS plus NATO vs Warsaw pact is very nice. I would like to have ability to construct or "research"... "Fortresses" that would hold ground in tme of heavy unbalance giving something to do to a huge enemy team and time to regroup to a small defending team for a while. That means 2 PAKs, one on each side to have the ability to become hard to crack nuts by having build inside them big Long Range SAM batteries. I mean S300 and Patriot like systems with medium and short range systems around them. The PAKs should be not in the center and exact location secret during the building. These batteries should be constructed while the sector is not under attack and should take multiple resources to build and a coordinated effort from the team. It should take multiple server restarts also so people would commit to them. Also the team could opt out of building such thing for a... blitzkrieg. Example: First you need to build 7 short range SAMs in a circle... the you can build 3 Medium inside that circle... then start accumulating resources to build the large long range SAM. Another thing, tech trees. Ability to "research" tech like things. Say... AIM120 or R77. Or planes... say a Carrier (movable by each team strategic command) with AI interceptors... etc.

Yeah... the cockpit shake is completely unnatural. A little is tolerable as feedback but just a bit over the edge and it reveals itself as it is. Unnatural. Our eyes and mind are smoothing the vibrations a lot. Making them reappear to the annoyance level makes the experience unnatural. Slider ftw. (mig21 does not have this option server enforceable because is useless).

Never ever had one with my 970 and as a matter of fact with any card. Assuming you have everyday a boot freeze because nVidia lied about 3.5GB vs 4GB of RAM is... a leap of faith.

LOL

Hi, thanks. It is my town from just over 2 years but I feel like at home. It used to be a mod around that did just that, replaced the texture of normal censored symbol with the historical one. Here is one example: http://forums.eagle.ru/showpost.php?p=2718270&postcount=3 He put the texture in each skin folder and modified also the description.lua file but you can also put that texture one time in the folder: \DCS World\CoreMods\WWII Units\Bf-109K-4\Textures\Bf-109K-4 and all default skins should have historical markings. The red folder needs to be created as you only have an archive there and is better not to modify it. The folder just gets loaded after the archive and the file in it will prevail against the one in the archive.

+1 Navigation is a bitch at first then becomes a skill...

A10C, FC3 Aircrafts, Ka-50 and P51 should still respond to personalized Server.lua from Saved Game files (even the one in config folder from main game folder). But anything related that you modify within game folder will fail Integrity Check when you want to go online. A huge FOV is not to be banned rather people that want it smaller should be able to do so without failing the integrity check. As I said, some people like that and some people use 3 monitors and that huge FOV is realistic and very good.

Yes and it only check the files within the game folder not user saved games folder. The server.lua I don't think can input settings to the game for modules that have their own views.lua files (the new modules) or at least my efforts were fruitless even in single player.

After 1.54 new Integrity Check system any alteration of views.lua from modules are failing the check. Server.lua apparently can't alter them Either (for stand alone modules after P 51 release). Problem is we have at least the Zoom axis that is set by default from 20° to 160° and while that is OK for triple monitors users or people that just want extra peripheral vision and don't mind the distortion, for others... me included, that huge 160° max zoom out level is a literally game breaker. Especially if we have zoom on axis the easiest is to go full min-max most of the times and max means viewing something like a warp drive action. Zooming in and out like this multiple times is almost nausea guaranteed. Examples: We need a sort of GUI like view settings to be able to personalize some characteristics without failing the IntegrityCheck. One idea would be to have a simple GUI toggle-able by a key combination (say RShift+Enter), something similar with Controls Indicator where we could have feedback to where or settings are in relation with the cockpit and default settings. I didn't wanted to complicate the image further but that indicator could have also the live feedback markers from axes and headtracking like different colored markers similar to default ones. If it could be made to be clickable would be awesome but maybe little steps approach is better. Then, the final settings be saved like with RShift+Num0 but in a different file which numbers are checked for integrity if they are within allowed limits.

Yes Devrim, all fixed and beautiful now! Thank you!! (I must spread some reputation before... :) )

It looks fine generally minus the mask for UV lighting which seems off a bit. Maybe you could use the original to extract labels for your gray version?

This recurring topic baffles me. First of all... the pilot body and the gear does obstruct things in real life... hence HOTAS commands. FW190 was designed to have all controls within reach and basically make the pilot look more outside the cockpit for enemy than search some lever or Button. Second of all because the pilot body obstructs things in cockpit there are no critical controls or gauges that are blocked by it in any cockpit. Real or DCS. You will not see the speedometer, altimeter, ADI or Artificial Horizon blocked by the body. Third, the pilot body in DCS would be nice to have animations that will make him raise the hand of the throttle to see the things beneath it but I think we can agree that is something that will complicate the development a bit more than DCS scope... for now at least. We will see what VR will bring onto the table However! There is a shortcut key (RShift+P default) that simply disables momentarily the pilot body making it disappear and basically revealing everything that it blocked. If someone LOVES to have a pilot body in cockpit this thing is the at the ready workaround. If someone doesn't love to have that body and complains about the minuses he's wasting his time for nothing. If Shift+P is too complicated change it to something simpler... I changed it to just "P" but one could make it disappear with a HOTAS button or a closer keyboard button than "P"... say "Numpad0" or "Space" (don't tell me you really fire weapons with space and complain about the problems the pilot body creates to hardcore simulation) Another thing someone can do is to edit a bit the lua files and make the command to show/hide the body assignable also to the mouse buttons and then modify the command to be available only while that button is pressed and upon button release the pilot body to be shown again. After that... you just need a mouse with more than 3 buttons as the first 3 buttons are somehow hardwired to the game for other tasks. Fourthly(?)... use 6DoF headtracking or VR. The amount of things not seen-able/reachable because of that darn body are reduced to simply caprice. And finally... someone could simply disable the feature altogether from Options and be done with it. Pilot bodies are here to stay exactly like 6DoF cockpits (remember how a simple representation of the cockpit was enough in early flight sims) and animated controls. Especially since VR is here. Soon we will want integration of fingers with VR and we have problems with an elbow. Seriously...

Great looking dashboard!! However can it be installed for default french? (I would have looked myself but is not yet available). If not... could it be possible to make for a french version also? Thanks!

I also have G940 and I observed this behavior since first 1.54 patch. Most of the times I have to press repeatedly a button until it is "sensed" by the game. In my opinion this appeared at the same time with introduction of hot pluggin and multiplayer input editing capability and somehow at least for the G940 it has a bit o lag. Workaround solution for buttons that simply refuse to appear even after multiple presses is to go to a different module and see the name (number) of that button already assigned and then pick it up from the list in the new module or where the user wants to edit. Worst case... pick by trial and error the buttons and test if they work. Once assigned the buttons react normally in the controls interface... meaning pressing them will make the list jump to the line where they are in use. I add a screenshot with the place the list is for picking the buttons in case someone didn't see it:

+1 for the show hide Also I observed that in Gazelle the FM radio volume shows as UHF volume in overlay and VHF volume is inverted. Not sure if it wasn't reported yet.

yes. at this address: \CoreMods\WWII Units\Textures\Bf-109K-4 you need to have a file called bf-109k-4_cross.dds that is not empty or "edited" and then you will see the historic markings. You need to search for such a mod somewhere in the forum.

I liked the voice acting. Reminded me of No One Lives Forever!

+1 Or a slider like Mig21 has

I was showing that there are two devices at the same time, TrackIR (becauuse of the interface) and FT (headtracker). I am pointing at the columns not individual cassettes. You said: "Other software (Free Track, Open Track, FTNoIR), worked by emulating TrackIR" You can see that OpenTrack "emulates Trackir" on one column and outputs its own perfectly working separate genuine interface on the other column (headtracker). So all those 3 softwares are able to emulate but not only that and even when they don't emulate, DCS works fine with them. As a matter of fact I preffer FT interface because TIR interface has the said above bug (which is why the discussion is connected). The columns disappear as I disable the outputted interfaces. They are not... something from history of devices connected or something.

It didn't worked. Many textures on the terrain look bad. I hope this will be fixed somehow.

I don't think that is 100% correct. First. The programs Freetrack or OpenTrack or FTNoIR can output their "numbers" on TIR interface... emulated or not. But they have their own interface that works with many games including DCS its called FreeTrack interface but we shouldn't confuse it with the name of the software. Secondly. DCS works differently with TrackIR than it does with Freetrack (output interface). TIR is used only aout 50% on each axis while FT interface is used 100%. True... you can adjust the settings to make those 50% on TIR to actually represent 100% and everything works the same. DCS works with both at the same time but will prefer TIR and use it if its available at the same time with FT. But ow (after 1.54) with that percentage "issue". After 1.54 patch 1 I observed also that DCS will fail to load if I use only FT interface and the tracking is not started prior to double clicking the icon. It wasn't like this before. And finally here is a screenshot where you can clearly see the different interfaces having different names and settings, I can make you a video to show you how I can deactivate them and what the game uses with same camera same software but only different interfaces:

Open track works for me. Still but with a strange "bug". If tracking is not started prior to launching the game the game will crash to desktop without any error in first half of second. If I start the tracking... it works. I am using Opentrack 2.3 rc49p0 with a headtracker.dll in bin folder that is there for ages. If someone want's to test it I can share it or search the version number or something. SkateZilla, I've seen you posting that "disambiguation" a while ago and I must say it comes a bit aggressive. It's like you want to say ED is actively blocking/bugging other free headtracking solutions to favor TIR or other technologies that are not free. I don't think is the case as it will go against a lot of customers. Maybe if you don't want to say/mean that you should sweeten it a bit. I understand that not-supported means if you have problems you are on your own which is fair enough if it doesn't mean sabotaging it. All of us will drop headtracking to some VR technologies at some point but there is no point in scaring customers for such thing.

Also the trees look bad (Starway's) like they load alow MIP very quickly. I don't have latest nvidia drivers... maybe I should upgrade to see if it solves something else I'll try to force everything from drivers.

OK, I had this problem and I think I solved it with the toggle mirrors. So before I had 22fps at a mission start. Also in flight the FPS was very poor. First I deleted (actually renamed so I can compare) Options.lua from saved games folder and after rebuilding all how it was the FPS jumped from 22 to 34 in same conditions Then I added the toggle mirrors command to default.lua from keyboard folder from input (I copied the line from mi-8 module) and when I toggled off the mirrors... bam! 60fps (max FPS for me as I use VSync and my monitor has 60fps). So definitely there is a problem with the mirrors (I think mirrors.lua from config does nothing as I tried to replace it with a low.lua... maybe there is a shader file for it now) and people that tried this fix maybe just didn't add the command properly so it didn't actually worked.

The problem seems to be that it is affecting only TIR. I want this feature but I am using opentrack with Freetrack interface ON and TIR interface OFF (heh... in the end choice is good it seems). I could turn off Freetrack interface and turn on TIR but that would also mean to modify my view axes length in all modules... till next patch most probably when I would have to do it again :) .