Wizard1393

Ok, will do :) Thanks!

I isolated the issue to the scripting engine function object:destroy() This code was used: wh = StaticObject.getByName('WareHouse 001') if wh then wh:destroy() end I use this code after the WareHouse has been "destroyed", when it's smoking and shooting flares forever and ever, why I want to remove it. Then it crashes DCS. For testing, I called the function before the warehouse is "destroyed, and it did not crash DCS. Also sorry to say the problem is intermittent. It does not cause a DCS crash every time, but almost.

Scenery Remove Objects Zone Scenery Remove Objects Zone Anyone know how I call this function within the scripting engine?

Yes. But that was 15 minutes prior to the DCS crash, didn't you notice? :)

Unable to interpret anything myself from the log relating to the crash. Had to remove the track to upload. Track was 20Mb. Can be supplied if requested. dcs.log-20180429-132235.zip

Don't know about your problem sorry, but moderator can move this thread to the MiG-21 forum.

I remember that someone once said that Nellis has a specific ruleset when it comes to choosing runway IRL. One is used for takeoffs and the other one for landings or something like that. I don't remember exactly what was said, but maybe it has something to do with this, why the same runway is always given from the ATC when landing.

Ok. Well, you made a request so atleast someone in the team is aware this would be helpful :)

Was coming to ask this question too. Found this. Any news Grimes? Would like super really help with missions where enemy ground groups spawn in random locations within larger zones.

Thanks bitmaster, u did what I didn't have the energy to do. ;)

Well if you're in the bin folder, just type the quoted command I posted above, without quotation marks off course and you're all set buddy :) If you are unfamiliar with basic command prompt commands, like traversing directories, just google it mate. You won't ever regret knowing the most simple and used commands like "cd.." and "cd mydirectory".

You're both welcome :) Happy to help!

Yeah, just drop a bomb on im, that'll shut im up :lol:

Start a command prompt. Navigate to DCS install directory and then into the folder "bin". Run command "DCS_updater.exe update @release". Finished! If you're currently on the latest open beta, nothing will happen, other than that you just changed the branch from open beta to release.

Actually I remembered wrong, watched the track just now. The helicopter was not landed, but was shot down at low altitude by the Hornet. My SU-25 was damaged by something, and I went down. Thereafter I respawned in a new plane, got to where I was starting or just about to start the engines and it crashed. Reproduceable, crash happens exactly the same when you watch the track. Thanks for the feedback Bignewy. Hope you/they can narrow it down and fix :)

2.5 stable crashed last night. No mods. SP. What happened right before the crash: I was in an SU-25, in hot on an AI Mi-8 that just landed in terrain to unload troops. I was beaten to the punch by a friendly AI Hornet the unloaded it's gun on the helicopter, destroying it. Game crashed seconds after. dcs.log-20180415-224949.zip

You have armed the bombs yes?

Shadows seem a bit better in 2.5, making it easier (still not easy) to see ground units out the window. In the Shkval it's pretty much the same, if not exactly the same. A tip is to edit your corresponding graphic settings LUA-file. I use "Extreme" so I edit the file "DCS World\Config\Terrain\Extreme.lua" I'm using these values: --Old Noise land_noise = { noisemin = 0.0; noisemax = 0.3; noise1front = 1000.0; noise1back = 30000.0; noise1top = 2500.0; noise1bottom = 2000.0; noise1PerSquare = 4.0; noise2PerSquare = 150.0; } It blurs the land textures compared to original values, making it easier to spot ground units in all views. ProTip: Make a copy of this file, edit the copy to these values, and activate it as a mod with the use of OvGME. Otherwise, it will revert back to original values every update.

About the popping nose wheel. Do not hold the wheel brake for long at a time. Brake in shorter bursts, max 4 seconds at a time, let it rest for 2 seconds repeat. Also, make sure you are not pulling the drag chute before the nose wheel has settled fully on the ground or the nose wheel will impact pretty hard when the chute opens.

Is this playable in 2.5, or if not, are there plans on updating it for 2.5?

Had this happen to me too yesterday. But I didnt pass very close to the last waypoint before the landing waypoint. Maybe that has to happen for it to trigger.

Yes. It doesn't do much. But a little bit. If u look at the comparison (now updated) u can see the difference in the bottom edge of the cockpit glass. The horizontal cockpit edge there is seemingly less aliased/jaggy.

Yes, I think there's obviously something wrong with internal cockpit lighting in most modules when deferred shading is turned on.

+1 cockpit instrument lighting is barely noticable in the KA-50. Same in other modules too, but the KA-50 is the worst, especially the autopilot channel buttons. And I agree, who's going to have DS off, as the trees look awful. I hope they can tweak this. If they just give the trees a darker color I would play with DS off to gain some FPS back. I need a new GFX card...

My findings: For MFAA to work, at least 2x MSAA must be selected in game. If in-game MSAA is OFF, nVidia Control Panel MFAA has no effect at all. The debate has been more about whether nVidia Control Panel MSAA has any effect in game, if in-game MSAA is set to Off. It does not. About AF (Anisotropic filtering). To clarify: This has nothing to do with aliasing (jaggies). It rarely impacts performance at all (in any game) and should therefore imho always be set to max setting (16x in DCS). Repsol2K: Please add comparison in-game MSAA OFF with nVidia Control Panel MSAA 8x to show people it does absolutely nothing, it does not work.