Jump to content

FlightControl

Members
  • Posts

    2070
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by FlightControl

  1. Try this tool here, a nice one :-) http://www.cpuid.com/softwares/hwmonitor.html
  2. If you are running DCS 1.5.7, then that is the root cause of your issue. The change from 1.5.6 to 1.5.7 has turned DCS into a mess. Huge performance problems. It is not your network. Do me a favour, run your mission, and show me how much fps you get on your server with 3D rendering off, out of maps mode, just on a blank screen. I also added the "manual" to disable 3D rendering, which you can find in your DCS world installation folder under \Program Files\Eagle Dynamics\DCS World\Config. graphics_readme.txt
  3. ok! Thanks gentlemen. There is another possibility. High CPU usage of the server ... If your mission uses a lot of AI, or as in the current DCS version, is bugged and is not performing due to a high amount of units, you'll have warping also. Internet connections can be the cause, but most likely this will be due to an overloaded server in terms of CPU. You can check the following: Check the amount of (logical) cores your server has. DCS runs the main logic on ONE CORE. You can verify this by looking at the task manager, and check the processor part. My machine has 4 cores, and 8 cores logical. The amount of logical processors is what matters. When your PC would has 8 logical cores, the maximum CPU load that can be achieved by DCS is around 13-14% of the total machine capacity. If you have 4 (logical) cores, it would be around 25%. Check your server, and validate the CPU load. If it is too high, you'll see the warping. There are a few tricks that you can do to optimize the CPU efficiency of your server. 1. Disable 3D rendering on your server. There are sufficient threads here that explain how to do this. 2. DON'T go into MAP mode. Go spectator, and then with 3D rendering deactivated, press F12, this will show a light blue screen, but your server won't generate any graphics and thus your CPU utilization is at max. 3. Press CTRL-PAUSE to check your FPS. If you have a blue screen and nothing is rendered, and your FPS is below 10 to 15 fps, then the server is causing the warping!!! In case of point 3, the only thing you can do is to reduce the amount of units and planes. You've reached the maximum amount of CPU load that DCS can handle. FC
  4. Can you maybe summarize the problem in words? A few sentences?
  5. Nothing new. This issue is exactly the issue that was reported initially. Every 3 seconds a frame dip ... Have a careful look at the video: -3Uh-eRexYo
  6. This is the CPU load of DCS just running the mission editor... My machine has 4 cores, 8 logical. So CPU load is about 12 for DCS, which is one (logical) core. When running the ME on a machine with 2 cores, you'll see about 50% CPU load. Seems to be a valid issue according to me!
  7. The mission editor takes a lot of CPU power, unnecessary. This is really annoying. The mission editor consumes unnecessary CPU power, dragging batteries on laptops. This is an issue existing for a looong time now.
  8. Now all of the circling planes have landed, and still no take-off from the awaiting planes. It sure gives some nice scenery. But it is a bit dissapointing that these planes don't take-off! Is this something worth to have a look at by ED please? Sv.
  9. Now this is interesting. One of the planes circling to land, got out of fuel and crashed. And now the other planes are landing! This after ... 45 minutes?
  10. And the queue is growing at the airport. Still no plane landed after 15 minutes!
  11. Check this out please. APC operations are not efficient / bugged. Check the following image. These planes are awaiting take-off. 3 planes are circling the base for landing. No other planes are in the air around the airbase. These planes are flying in a continuous circle, and aren't landing. I have run this for about half an hour. The circling planes don't land, and the planes awaiting takefoff don't take-off. Deadlock!
  12. Some more fixes, ensure you have the latest version. This one upon request for issue resolvement for Ramsay and Thepikester. The coordinate management menus have improved. Settings management now has modified Lattitude Longitude coordinate representation options, that are federated and formatting any coordinate information messaged using the moose framework. Now the LL menu is replaced by 2 menus, Lon/Lat Degree Min Sec (LL DMS) Lon/Lat Degree Dec Min (LL DDM) [*] LL Accuracy menu options are only available when LL DDM. As agreed, for LL DMS there won't be any accuracy. Optimized the menu settings logic. Default menu setting is BR for A2G and BRAA for A2A. You can download the latest release from: https://github.com/FlightControl-Master/MOOSE/releases FC
  13. I hope the wheel is round enough for you, hehe. The waypoint stuff in escort needs to be fixed, though. Also suggest to many to explore first what is in the box :-)
  14. http://flightcontrol-master.github.io/MOOSE/Documentation/Spawn.html##(SPAWN).InitGrouping Put a template of one plane. Use InitGrouping( 2 ) and I believe it should spawn 2 planes. Put a template of 4 planes. Use InitGrouping( 3 ) and it should spawn 3 planes. But take care, I don't think you can use InitLimit (yet) with InitGrouping.
  15. What you mean with... Randomly / Unreliably? You mean: Moose does not work as expected, ir your script works as expected?
  16. CLEANUP_AIRBASE? Just not sure if I built this functionality in the module. If not, it is a good idea to have this function included. Look guys. Am right now away from home. When I get back, which is in a week, I can look at this issue. This can be fixed. Hope you understand.
  17. Hi Shadow, there is a known issue with some of the planes just landing and not de-spawning. The root cause will be somewhere hidden in the logic. I'll find it but I just need to look for it or discover what isn't working properly. It will take time to find the cause. Just use the modules as they are great. As time goes fine tuning will happen. Thank you for reporting. FC
  18. The default is endless....
  19. Guys, Pls have a look here: https://forums.eagle.ru/showpost.php?p=3222080&postcount=635 Sven
  20. You can switch off the trainer with the menu.
  21. Thanks to all Before I go away a few days, allow me this. Got this little object in a box a few weeks ago delivered at my home. Was thinking what would be the best way to say thanks, and decided to say Thanks to all the users and the contributors! Most of you knew about my situation, and you stayed and supported the project. It kept me busy while recovering from a severe illness. You guys are amazing. thank you! Sven Just an open question, what do I need to do with this object? Is it a trophy that is sent around year by year?
  22. Yup. thanks!
  23. Okay ... Remember this thread? I have a question, and it involves detection. Got in MOOSE this slick DETECTION classes... I have been working on it and improving the mechanisms how the DETECTION classes "recognize" the objects it detects. And I've noticed something really strange... It concerns the detection of ground objects. There are basically two kinds of ground objects: - The ones that emit radar signals. - The ones that don't emit radar signals. Targets can be detected in many ways: - Visually - Through RADAR - Through RWR - Through IR - Through Data Link - Through Optical Equipment An MQ-9 Reaper is able to detect ground targets from very far, like 120km distance, knowing exactly its type name, distance etc. This is the case when it detects targets using all available detection methods. So I went to search, why that is. Can't be. The Reaper seems to be able to detect all targets from a far distance, when it uses the RWR detection method. Now I think that is a bit of bollocks, how on earth can it detect a BMP-1 at 120km distance using RWR? A BMP does not emit radar. So what I am going to do, is to check that if the target distance is over 15km, AND, if the unit is not emitting radar, that it can't be detected by a Unit using only the RWR detection method ... FC
×
×
  • Create New...