Jump to content

Lynnux

Members
  • Posts

    64
  • Joined

  • Last visited

Everything posted by Lynnux

  1. Thx for the video. Possibly the F-18 was notching and -1 elev would have been the better setting when it turned into me. Hi setting might detect it faster in this moment but I think the better solution is having a wingman to be able to spot a notching plane in first place ;-)
  2. Just flew in multiplayer, alt 10800m. F-18 in front flying directly towards me, alt 9500m, range 60 km. Radar was on ILV, mode 100 km, forward and 0 elevation. F-18 fired missile below 40 km. No rader blib until missile hit me. Does the J-11 have a radar ?
  3. Just installed DCS on a new PC. Btw. entering multpiplayer games takes noticeably longer now in 2.5.6 stable than in 2.5.5 stable before. ED recommends not to simply copy DCS and run it but do kinda fresh install via the method posted in the FAQ (https://www.digitalcombatsimulator.com/en/support/faq/): Unfortunately this method didn't work for me but what you still can do in this case: 1. On your current PC do a DCS World repair (should be in the start menu in the DCS folder). 2. The repair tool will ask you to either keep the files not belonging to DCS or to remove them. If you remove them, DCS will place them into a "_backup.xxx" folder below the "DCS World" folder, so they are not totally lost ;). Removing them will give you a cleaner DCS for the installation step. 3. Save your DCS on an external harddisk or whereever you have still space. It were almost 200 GB in my case. Can be zipped or not but you have to be able to access and unzip with your new PC. 4. On your new PC, install DCS freshly via the web installer. Let the DCS launcher run for some time so it will build the folder structure in the "_downloads" folder below "DCS World". I noticed that all the files are unpacked there and ready to just being copied. 5. Copy those folders from your original DCS into the new "_downloads" folder. Just copy those folders, no additional ones (like the _downloads, _backup.xxx and SRS folder). You can skip the files already inside there. 6. Continue the installation with the launcher. It should check for already downloaded files and just copy the files from the "_downloads" folder and only download some missing files. Remark: the installation is usually done in two steps, first DCS World then the additional modules you purchased. 7. After the installation is complete, do a DCS repair again. 8. Delete the remaining content in your new "_downloads" folder. This will still speed up the installation, especially if you have a slow internet connection. 9. But that's not all because all your config files are in the "...\Users\<Username>\Saved Games\DCS" folder (short: under "Saved Games" in your user folder). You can either just dumbly copy all those files or clean it a bit (tracks, log-files, multiplayer server favorite list, ...). If just copying, take care that the path to this Saved Games\DCS is the same as before or you may have to adapt some paths in the config files. Anyways I had to reapply all the joystick settings to every plane in the new DCS. They are usually in "...\Saved Games\DCS\Config", so this one is important. Beware that there may be other folders in the "Saved Games" depending on your purchased modules. 10. After applying your Saved Games\DCS start DCS. Enter a multiplayer game requiring an unmodified client, this will tell you immediately if your client is ok. If not, do a DCS repair again. Useful tools: a better text-editor, a tool to zip/unzip, large harddisks ;) Good luck !
  4. @RagnarDa Oh, did one simple test: Flew with RWR off => no crash on autoshutdown. So yes, it looks like it's the data collected by the RWR in my case. This occurs since the update to 2.5.6 (stable here). Two days before the stable update I downgraded my old PC from Windows 7 to Windows 10. The new system was freshly installed with Windows 10, so unfortunately I can't tell you if this problem occurs in Windows 7, too.
  5. I have 32GB RAM. Btw. I also have this bug after stopping via thrust reversal only, so the brakes don't seem to be involved here. The coordinate system doesn't have any influence, too. The number of memory pieces vary (were also between 800 and 1000) but it's always the "RWR: bad allocation" error in my case. On multiplayer servers there are often a lot of ships, SAMs and escorts for AWACS and tankers, so the RWR is playing music all the time. Shall I try to delete the Viggen in the mods directory and reinstall it ?
  6. Same issue here and I got this error everytime now after flying a mission on a multiplayer server (so far only air to air in 2.5.6). In my case the error occurs when automatically shutting down the Viggen with "Windows+End" in the parking position. The hangup/crash usually occurs after the first (Start of autoshutdown message) or second (switching mode to BER) message. Edit: Btw. I also applied autostart and autoshutdown after spawning with keeping different systems on after autostart. No crash this way, autoshutdown seems to work well if the plane didn't move or fly before. And I have the decimal coordinate system on the map enabled. Will try if this still happens with the standard coordinates. It also occurs on two different PCs. Lotsa of these cartridge messages before, I have to delete the cartridge files / Viggen folder ;-) 2020-06-08 18:13:26.178 INFO VIGGEN: Release brake! 2020-06-08 18:13:26.677 INFO VIGGEN: Set brake! 2020-06-08 18:13:31.094 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:13:31.094 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:52.985 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.712 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.712 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.783 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.807 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.807 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.807 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.829 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.829 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.875 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.892 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.892 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.892 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.909 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.910 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.910 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.924 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.924 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.924 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.942 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.942 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.942 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.958 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.958 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.958 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.973 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.973 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.977 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:53.991 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:53.991 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:53.991 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:54.011 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:54.011 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:54.024 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:54.040 INFO VIGGEN: Dumping 1826 memory pieces... 2020-06-08 18:14:54.040 INFO VIGGEN: Analyzing ELINT data. 1826 memorypieces. 2020-06-08 18:14:54.080 ERROR VIGGEN: Error thrown in RWR: bad allocation 2020-06-08 18:14:54.082 INFO EDCORE: try to write dump information 2020-06-08 18:14:54.083 INFO EDCORE: # -------------- 20200608-181454 -------------- 2020-06-08 18:14:54.083 INFO EDCORE: DCS/2.5.6.49798 (x86_64; Windows NT 10.0.19041)
  7. Hi Dhyran, welcome back !!! Just saw your server… and damaged a ship there ;-) Flew with Loose Deuce in Aces High II, was really fun. Stopped flying at all in 2009, though, and returned here to DCS to learn it again ;-) Your squad logo: LD in a SEC escorting bombers: This Swedish guy was really good:
  8. Have the same issues in the trial, will try that immediately. I'm running stable version but that doesn't seem to make a difference for M2000 (last updates 2018 ).
  9. You need to contact support to get a serial number for Ka-50 if you mean that with "non-working". I've been flying it in stable for 2..3 days now.
  10. Kann ich in diesem Artikel nicht herauslesen. Außerdem ist das Thema hochpolitisch, wie die meisten Waffen(ver)käufe, das wollte der OP doch weglassen ;-)
  11. Had the same issue as OP with losing radar lock and after the trial period I came to the conclusion that maybe the history was too short, especially when using 6 bars and 140°. Another issue was that I couldn't get the laser pod working. Third issue I solved after shooting two friendlies was how to switch the IFF on. Two days were simply not enough to get all the stuff working. Otherwise I like this plane, especially the FM. Feels pretty lightweight. Visual carrier landing without ILS and coming in in a turn worked well even on the very first landing.
×
×
  • Create New...