Jump to content

firmek

Members
  • Posts

    1370
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by firmek

  1. Now, that's a hudge overassumption but... There are a few airframes in DCS that have exceptionally good quality models as for AI only units. One of them is the Kiowa. Tornado also if I recall correctly. Just a big guess but this makes me thinking if those are not already a "thing" in TBS: http://www.thebattlesim.com/images/Vehicles_and_Weapon_Systems-13.jpg
  2. If I recall correctly the full story was that the FC aircrafts can't use nav systems unless the flight plan has been created in mission editor. For all others it shouldn't be an issue.
  3. I suggest follwing priority: 1. Upgrade GPU, 1070 at least. IMHO 1060 is not worth the money compared to 1070. 2. Get SSD, don't worry about their durability. You'll change your PC before it dies. Install OS on it and if you want also DCS. 3. As already noted changing CPU would be quite expensive in your case as you'll need a new motherboard and RAM. If you still want to upgrade CPU get i5 instead of i7 and invest saved money in 1 or 2. 4. 16 GB RAM is ok for the moment for DCS
  4. Might be that I'm not reading it correctly but based on what you've wrote I would judge it's more of an issue with the head tracking device. If it would be the movement limit, the in-cockpit head would hit it and shake around it but wouldn't jump to a new position.
  5. Might be an effect of watching it on the video. For example occasionally I'm getting uncomfortable when watching youtube clips recorded from VR. Frankly speaking such option might be controversial as it can give slight advantage over the real plane.
  6. It has been already stated many times that Normandy is not a 1.5 and 2.0 merge. We will have to wait for it some time at least untill the new Caucasus map is ready.
  7. Probably but lets wait for the announcement on the forums. Normandy next week is confirmed. Let's wait to see if there is an update for 2.0 today.
  8. That would be also my bet.
  9. I'm taking specific statements from your comment but think how long the Nevada is alpha stage...;) Anyway, my comment was mainly about the fact that people still confuse Normandy and 2.5 release which as underlined many times by ED are separate releases that will come in sequence most probably with some substantial time in between.
  10. I don't think so. Unless there has been some big news the plan since quite long is that 2.5 is not the Normandy release. First the Normandy release on 2.x brunch (now named as 2.1). Second, upgrading the Caucasus map. Third the merge of 1.5.x and 2.x.x into 2.5.
  11. +1. Let's not mix aeronautics R&D process with a software development life-cycle. In software development a projects that woud reach a perfect solution with first release candidate version just doesn't exist (unless it's a "hello word" application). The more complex and with more unknowns, the more testing, feedback and fixing iterations will be required.
  12. I have quite a few modules already. Never had any issues with the purchase. Don't see anything complicated with it. Just stay with either standalone or steam. The fact that DCS has a standalone version is one of the best things about it.
  13. +1. You've put in a nice, political way ;)
  14. I don't think it's possible to do it this way, most probably it'll crash. I can check it later if I get some free time but I wouldn't hope for it. On the other hand, assuming that there is no snapviews.lua file in user folder, every time you generate a snapviews the process actually takes the most up to date values from the respective DCS folders. Afterwards you can go through it just change the values at index 13. Takes a moment but it's not a total disaster. The values stored in snapviews and view/server.lua should be controlled by in-game options. Unfortunatelly such functionality doesn't exist jet but working with snapviews.lua and server.lua stored in user folder is usually a single time effort. Afterwards it's just a short updates from time to time.
  15. Much better would be to have a different kinds of nav aids available as an mission editor resourses. This would allow to drag and drop them on the map in any location or edit as an airport nav aid. Generally in a similar way as it's possible today with units, static structures and warehouses. From this it's an easy shoot. Just setup nav aids on the map and save as a template (for instance Normandy WW2 nav aids, Normandy 70's nav aids, etc.). Having the nav aid as an mission editor resource would allow also to access it via script. Just imagine a scenario that the RSBN statin in Beslan gets replaced with TACAN if the airbase gets captured by blue in blue flag.
  16. You can take an user made version of server.lua with more modules added by copying their settings from respective views.lua from here. The default FOV is stored in the snap views file.
  17. Basically the server.lua is a user customization which as far as I can tell by default is not created with clean installation. All planes start with view settings as done in the internal, DCS files, most in "DCS World\Mods\aircraft\module". If you place the server.lua in the user folder the game, provided that it contains a valid configuration for the aircraft the game will read it from there, overriding setup from the DCS folders. In other words, unless you've done something wrong it should work. Usually if it doesn't, especially for multiple aircrafts it can be a syntax error. The advantage of server.lua is: + green for IC, you're not modifying original, in-game files + it's gives an easy way to apply the same config values for all planes (personally I hate to have a different min/max zoom or head movement between planes) + doesn't get overwritten by updates Negatives - doesn't get overwritten by updates :). That was an possitive but the downside is that if there is an update/fix for an module it'll not work. You have to check manually from time to time. On the other hand the view configurations are mostly not changed from the release date.
  18. Depends what is your preference. I would still prefer 34'' 3440 x 1440 over 4k as it's possible to get an IPS panel with 100 or 144 hz and G-Sync. Others may not pay so much attention to panel technology, refresh rate or adaptive sync. The resolution should not be the only decision factor when looking for a good and rather expensive monitor.
  19. Another option. Unless the moniotors that you have are great, instead of 2 displays get a single one bigger, ultra wide with a higher resolution.
  20. I'm lost why the fact whether the DCS is a combat not a GA simulator is discussed as a decisive factor for a realistic weather. Be it a 737 or a fighter both fly in an air and should be affected by it. DCS has a state of the art flight models, the best out there. At the same time flying in atmospheric environment simulated in rather a simplified way reduces the overall experience. IMO putting a lot of attention into flight models and taking shortcuts in simulating the environment forces affecting the airships kind of contradicts each other.
  21. This +1. After all the time since the update, having all steps how to run the activation clearly documented in pdf file and on top of that "for dummies" like instructions repeated many times in this (and "April") thread people still fail to run a simple procedure. Amazing is the fact how those folks fly a module described by an almost 200 pages manual... :lol:
  22. I don't even know where to begin with commenting this statement. 2 hours to make a dedicated server... I think people should grow some respect to the work that others are doing.
  23. As above, aside of turning your head you'll also need to lean to a side. You could make your "shoulders" wider, which will offset head to a side more as it's being turned but at some point it starts to feel unnatural. To do it just change-increase the line: local gShoulderSize = 0.15 -- 0.25 Shift head left/right when view angle is more than 90 degreesSomething like 0.25 should help, though you can go higher. Note that if you're using this file "as is" this setting will affect all of your aircrafts.
  24. I think it's more essential problem than just the fact that the map is a paid module, even including the necessity to purchase a server copy. Nevada is a really specific area - meant for red flag like scenarios, trainings, equipment and weapon testing. Might be a personal thing but It's hard for me to get an immersion feeling when flying on it with any other purpose and even then it feels off seeing an eastern bloc units, especially a vintage ones and actually shooting them with live ammo. Anyway, it comes to the mind-set but I just can't get rid of a question "how to hell did the Russians get to the Nevada" out of my mind every time I join the map. Aside of that NTTR is set in a modern times which in result kind of makes it to feel right when flying an F-15 or A-10C (and maybe Mirage). It's always better to have something rather than nothing and while being aware about the history of the NTTR map I tend to have an opinion that the whole idea about it is a bit missed. I'm quite sure that despite of having to purchase a server copy maps like Normandy or another potential ones like the Vietnam or a Fulda Gap would get more interest, more MP servers and higher player numbers.
  25. Another point is that the sight reticle is a bit off: https://forums.eagle.ru/showpost.php?p=2999037&postcount=4 Generally, the outer circle is too wide while the space between horizontal lines (distance adjust) too narrow.
×
×
  • Create New...