homepage Forums Air Combat & Civil Aviation DCS World Eno's Firehouse and Crew's Hollo Pointe Server Lounge

My mistake. I was talking about the Kh-58 ARM and then transferred my thoughts to the laser guided Kh-25. Both of which I was having problems getting to track/guide.

-Jeff

I tried to test this on my new mission in the Shampain and did all my experiments from the Mission Editor in SP. The first test was with the embedded .miz file removed from the mission file. When it came time to load the mission per the event trigger nothing happened. No error, nothing changed - good, OK - at least nothing bad happened, but an error message would be nice, or even better a message at the time of mission edits compile as to a missing object; then again I think it is really weird to embed files like this - but the designers most likely see it as an advantage in development.


Eno, I'm not spending any more time on this. I think it must be tested on a MP server, not in an SP Mission Editing Fly session. Hollo Pointe is busy so I am going to beg off on this.


But I do offer caution as to the way missions will hold embedded .miz files for the Load Mission events - these next-mission arguments need to be reset after the next-mission is edited. If you don't reset the Load Mission event to the latest next-mission then you will/may/? load the down-level embedded version.

So that goes right to your question, Eno.

WC

^^^ It does make a difference in the mission file size. I made changes to The M4 and by deleting the .miz, saving, setting the Load event I got the file size from 10,992KB to 5,523KB.

---> edit Because I think the embedded .miz files can hold embedded .miz files. Ummmmm, whatever.

WC

I was more just wondering from experience- not expecting you to test or anything. Thanks for passing on those learnings, however.

I have removed reload triggers and re-saved- and it cut back the size of the missions. Unfortunately it doesn't really lead to a fluid experience but I guess that's why we have admin mods to load the next one. Except in the case where we have your campaign and the flag values determine the victory condition.

I guess you could just load a text that says "Blue is victorious- please load mission Y." And just leave it on for 10000 seconds.

Thanks again crew.

Nevermind.

Eno..Just played your new mission..Fantastic. Worked great! You the man

I was on last night and did a little experiment. I was flying along at 10k my frames dropped to something like 9-12. I was like wtf. I look behind me, frames goto almost 30, I look forward and back to 12. I then saw all the smoke in the distance from the ai making their initial attacks. Musta been 20 ai planes in front of me.

Wheel was that the mission I was in with you tonight? I thought it was great too. If so nice job Eno!

Zesti -




Back on Zesti Highway to define a standard mission template... want all campaign missions to have the same Mission Briefing formats.

WC

Not mine guys-I think that was houdinis new one that blooze was talking about one. The second chapter. I've heard really great things about it.

Unless something else got loaded? In which case... Thanks!

also from rider1 included in a thread below it looks like he may have solved the smoke problem:

http://forums.eagle.ru/showpost.php?p=1715708&postcount=138

That was in response to the issues caused by all those vehicles burning in that full throttle mission- I think it was wild or blind who killed all those AI. Anyway- definitely worth a shot.

Hey Boss.

Thanks for hosting my missions. I'm working on mission 3 at this time. I also have a couple of patches I need to issue for mission 1 and 2. I'll send you the new missions once I have them fixed. Patches as follow:

On Mission 1:
- There is an overlap on a message that announces the arrival of enemy reinforcements. Due to a message that arrives at the same time, that important announcement gets shadowed. That creates a delay on the attack from the players to the enemy units arriving to reinforce. That's a timing issue with one of the switches.
- Weather will get adjusted for computers with lagging problems.

On Mission 2:
- I will adjust the route on both sweep teams to avoid the glitch where a unit start running in circles, delaying the rest of the units.

Also, I would like to report a small incident I had on your server yesterday:

last night (April 03/13), around 9:00 pm Central Time, I saw a new player, he was kind of cool at the beginning, you know, reporting what he was doing and stuff, but later he came up with some kind of attitude. I had a couple of encounters with him, that I decided not to escalate, mainly for two reasons: 1- Not creating a discussion in the middle of the game, and 2- Because I'm to old to discuss with this player. His tag starts with FR.... or FRE... FRA .... I can't remember right now. Molassess was also there, he can tell you. I'll suggest you keep an eye on him just in case you see him again.

This guy asked me to provide him with some coordinates, which I gave him in the form of Degrees - Minutes - Seconds. He basically said that he needed the coordinates in the UTM format, because it was impossible for him to enter them on his Nav computer. Dude, I read the ENTIRE A-10 manual. Took me 7 days, every day, sitting on the cabin for hours, doing nothing but exploring each one of the instruments. I can enter coordinates on any format without the need of ANY conversion on my Nav computer without any issue, and I was going to give him the steps to enter them on any format, but he basically said, and I quote, with Capital letters: "I KNOW WHAT I'M SAYING AND YOU DON'T!". I replied with a soft: "dude, calm down, no need to yell", and he ceased the fight.

You know me, I'm all about having a great time, add as much realism as possible, and play with the good fellas, but situations like this cause a lot of disturbance in the force.

I'll keep you posted about the patches.

Thanks again, bro.

Houd.

On another note I've adjusted Full Throttle slightly. As many of you may have noticed there is a relatively "random event" that happens at some point in the mission.

It took some time but I've implemented some changes to the triggering system that will only allow that "random event" to happen if there are a certain number of players in the area. I'm hoping that will at least give everyone a bit of a fighting chance.

Once the event happens, everyone has some time to get back to base to rearm and refuel and then take a fight to the enemy.

We've also possibly found a problem with the fuel trucks- and though I liked having them in there I'm removing them from missions so that they don't drag everyone's frames down.

Hi Houdini,

Eno's Firehouse and Hollo Pointe servers are running the Slmod that has a Ban feature and a Chat Log.

As long as the offending person types in some chat text or makes a team kill that gets captured to the Chat Log, we can go through the log and find the guy's UID and IP and add them to the Ban list, if the log entries warrant it. (I wonder if turning off the notifications would stop putting team kills into the Slmod chat logs.)

Anyone can report an incident by sending Eno and/or me a private message with the player's name and approximate time of the occurrence.


If offensive issues are being made on the SimHQ Teamspeak channel, then note the time and date and user name and contact one of the SimHQ admins. You should try to record the TS conversation to give to the admins, maybe a screenshot, too.


WC

Hey Whiskey-Charlie.

I think the situation didn't escalate because I didn't follow his attitude, as I was trying to be polite with the new player, especially on a server that is not mine. But it's alright, I ain't even mad

I'll follow the procedure next time in case this kind of situation arises. I just don't want to see a good server falling to the dark side of the force.

Check yesterday's chat logs between 7 and 10 pm CST if you want to, just for curiosity. Or search the logs for the string "calm down" and go up from there:D

Thanks again, bro.

Houd.

Eh houd we must have written our emails at the same time. I saw the interaction with the member in question and I've seen the same attitude from him on the site. I was auditing the log to see what was going on and I saw the whole thing. Not the kind of attitude I'm at all interested in for the server. I'll send him a note and tell him to stow the 'tude or take it to a squadron somewhere where they can out-knowledge each other. Thanks for keeping your composure.

Anytime, boss.

Thanks

Houd.

next time just whisper, your balls are showing...

Houdini, sorry for any shift key nonsense. It's just frustrating to try to explain a point and be told a little condescendingly that I'm saying what I'm not saying as you'd already concluded that I was mistaken. For every hour you've spent reading the manual I've probably spent ten. That's not to say I'm always right but at least engage in a discussion I'm trying to have with you about it instead of saying "No, you're wrong." That will, as seen, tick me off. I also didn't run away, I had to go and couldn't be late. I tried to explain what the academic issue was to whomever was in TS3 at the time (I think Molasses) as I left. I also got "target snatched" about 80% of the time on ingress so I spent a lot of time setting up so some yahoo at 3,000' could slam yet-another-maverick into my desired target. Wasn't in the best of moods already.

When you offered those coordinates I thought great, thanks. When you typed them in DD�MM'SS'' format (it's quite a bad habit to omit the symbols, btw) I said it would take a second for me to convert them into the CDU L/L format (which as we know is DD�MM.MM'), mentally but I had only a few synapses to spare flying low over possible MANPADS. I'll try to be brief and clear because it isn't the most straightforward distinction.

Say you provide a latitude 123�45'56''. If I were to blindly enter 1-2-3-4-5-6-LSK on the CDU, it would enter in 123�45.56' which is not the same as 123�45'56''. It would be close-ish, but not correct. The maximum error due to this mistake is 23.6'' (the difference between 59'' and 0.59'), about 2390' error if 60'' = 1nm (in longitude the error will usually be smaller).

As for "keeping any eye on me" that a complete overreaction. I've never TKed. I actively seek teamwork. I actually read the brief. I don't takeoff the wrong way or from taxiways. Getting your feelings hurt because I said you're wrong isn't the end of the world. Your ego will recover. Crazy people wanna make pariahs out of anyone nowadays...

Check this out -

http://www.windtee.com/aviation_t-shirts/a10_warthog_gau8_avenger_t-shirt.cfm

WC