reiser

First off, your Init's need to be before ANY Spawn* functions. Second, you need to hook into the events system to start/stop the spawn schedule. You're on the right track with the triggers, but what you need is a SCHEDULE to continuously check those triggers. The triggers can be triggered via menu options or what not later. You can even then use MISSION to have the menu's to trigger the trigger to spawn.

I too wish the replay functionality was up to par. Up until now, almost everyone uses TacView to replay their mission. For screenshots and video, Kang is right, pause and remove the status bar, align the camera, record, unpause, get your shot, pause, stop recording, repeat. The replay system right now records inputs over time. When it plays it back, those inputs are fed to the sim at the correct time markers (except when it's not, and your plane goes nuts-o). What I would love to have is a replay system that records events instead of inputs (kinda the same? sorta?) and we can replay those back using a timeline scrubber. Heck, hire the guy that made TacView to do timeline scrubbing and event tracking. TacView does this wonderfully. I honestly don't care about how big the replay filesize is over how well a replay works. I'd rather have a replay system that works forward and backward in time than have a small replay file.

I hear a lot of could and will in those videos. I mark my videos as not for kids. That's my responsibility. If the FTC flag my videos, than I'll deal with the FTC to explain my position. So far though, this is just a bunch of people pontificating.

This just bit me today... I wrote this all elaborate lua script using MOOSE, MIST, etc and it works great testing... I put it up on the server... S_EVENT_PLAYER_ENTER_UNIT never fires and so the entire map is just empty... In the ME when I run it in SP mode, that first event triggers spawning of the entire map for campaign tasks and things dynamically. But without this event it just feels like a completely non-scripted empty MP mission. :(

I'm writing this to formally apologize in front of the community for jumping to a conclusion last night in the heat of battle without assessing the facts. Last night, on the MDS CoffinDodger's server, my squad and I were flying, testing, a mission and made it available to the public. A bunch of people joined and we had a good time. I was flying an F-15C to balance the powers (most of the MDS crew were on Red side). Beamscanner was also with us on Blue, flying the F-15C. 20 minutes into the flight, after a few tangles with some MiG's and Su-27's, I was shot down by two missiles while I was trying to lock up another target. A brief look at my RWR gave me the impression that it was an F-15C that shot at me. I looked at the map, and incorrectly deduced that Beamscanner was the culprit. After getting angry and calling him out, I checked the TacView track. I was completely wrong. Turns out in the heat of things he WAS in-front of me, but turned away as I was trying to lock up that other target and my poor SA during that caused me to be hit by 2 SA-15s. So Beamscanner, this is my formal apology that will live forever here on the ED.ru forums. Contact me on MDS and I'll make it up to you. -[MDS]-B reiser #04

Memory Leak This is a constant issue. There is a memory leak in 1.5 beta that prevents servers from hosting for more than an hour or two. This is a show stopper for many of us. I have a mission that not matter what, as soon as 4 or more people join, it starts leaking 1k-1mb a sec. indefinitely. This should be your number one priority. Memory leaks are critical.

In the 109, 0 means 0 trim. There isn't aileron trim, or rudder trim, only elevator trim. 1 is 10 degree trim, -1 is -10 degree trim.

I've been flying the BF-109 variants in sim's for a long time. I even flew with the good chaps at ACG and their epic battle of britain recreations. I've always flown with manual pitch control. Always. The trick most people forget is the wheel lock. When lining up on the runway, move forward about a meter or so and turn wheel lock on. This locks that back, grocery store cart, wheel that keeps the plane stable during takeoff and landing. Takeoff: WHEEL LOCK ON! 1.2-1.4 ATA, Pitch 12:00 (unless weather, then 11:30 to push more) Climb: 1.2 ATA, 2500 RPM, Pitch 11:00 (reduce by 0:30 for every 100kph over 200) Climb Angle: 10 degrees up( when following above climb rules, maintains speed ) Maneuvering: RPM 2200, 1.1 ATA, Pitch 10:00 Downward Maneuver: RPM 900, 1.0 ATA, Pitch Increase Upward: RPM 2400, 1.2 ATA, Pitch Decrease Max for Maneuvering: RPM < 2600, ATA < 1.3 (if you let these get above those numbers, bad things happen to engine, important to keep eye on dials during maneuvers) Landing: Pitch 12:30, RPM 900, ATA 0.8, flaps as needed to maintain 200kph and 500m on final. Touchdown: Reduce RPM's completely, level out with a little flare to reduce your vertical speed. Land with first pair wheels, wait, wait, wait, and pull the stick back to drop the tail. Navigate with slight toe brake corrections. As soon as you are below 30kph, TURN WHEEL LOCK OFF!

See DxDiag.txt attached. DxDiag.txt

CTD's all day Initially, the beta was good. Flew around, shot some people online, played with my beloved BF-109 a bit in a single player mission. However, now, whenever I fly my baby, I get constant crash to desktop. 100% of the time. Here's my logs... 00567.735 INFO DCS: try to write dump information 00567.744 INFO EDCORE: # -------------- 20151006-050405 -------------- 00567.759 INFO EDCORE: � 00567.766 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 0FDE9680 00:00000000 00567.770 INFO EDCORE: 00000000 00000000 0000:00000000 00567.782 INFO EDCORE: 0FDE9680 00FBEB00 0000:00000000 ?setShader@DX11Renderer@RenderAPI@@UEAAHPEAUIShader@2@_K@Z()+60 00567.790 INFO EDCORE: 180E1E6C 00FBEBC0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+254C 00567.793 INFO EDCORE: 180E1A4D 00FBEBF0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+212D 00567.801 INFO EDCORE: 22AB40FF 00FBEC20 0000:00000000 ?DrawObjects@DXRenderer@Graphics@@UEAAXPEAPEAVRenderObject@2@I@Z()+6F 00567.809 INFO EDCORE: 3692DEEA 00FBEC60 0000:00000000 ?DrawZWrited@RenderParserImpl@@QEAAXXZ()+11A 00567.810 INFO EDCORE: 369300EA 00FBECA0 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+1B2A 00567.811 INFO EDCORE: 36949C7C 00FBEF80 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+BCC 00567.811 INFO EDCORE: 40577D04 00FBF010 0000:00000000 00567.812 INFO EDCORE: 4057B44E 00FBF070 0000:00000000 00567.812 INFO EDCORE: 40591BE4 00FBF0A0 0000:00000000 00567.813 INFO EDCORE: 40591B34 00FBF0D0 0000:00000000 00567.814 INFO EDCORE: 4063B4BC 00FBF780 0000:00000000 00567.815 INFO EDCORE: 4063D365 00FBF7C0 0000:00000000 00567.817 INFO EDCORE: 3FBD2D92 00FBF7F0 0000:00000000 BaseThreadInitThunk()+22 00567.817 INFO EDCORE: 42419F64 00FBF840 0000:00000000 RtlUserThreadStart()+34 00568.038 INFO EDCORE: Minidump created. 00568.094 INFO DCS: try to write track file crash-logs.zip