Stuart.G

** brushes off the dust settled on his Forum account ***
 
Hi there guys,
 
It's been a long while. 
 
My name is Stuart and Ahoyworld was my life for 2 straight years before my uni. I remember the great times this community gave me almost every day playing EU3 and later AWE. It was amazing. Being known as a horrible shot I almost always flew transport and to this day it remains one of my fondest memories, shuttling troops to and from as Vortex 1 or 2 and later Angel 1 and 2. I remember that flying formation as two aircraft was the most rewarding and fun thing to do at the time. 

Well, with my uni starting I had to sadly take a step back from Arma as a whole and while I still played games, I never had the time to dedicate and come back. Until now. 
While the community seems to have evolved and had many ups and downs (atleast from what I could see by every so often stalking the forums) I am so happy to still see it around 6 years after I joined. (Atleast thats what my TS account is claiming, (22/01/2015) baby!). 

Eventhough I do not expect to experience the same gameplay I had back then, I am happy to be able to dedicate atleast some time back to Arma and there is no other community I feel I could be happier joining again. 
 
So hello everyone, new and old. I hope I can come chat with you on TS and maybe even see you around on the battlefield. The constant missions running currently seem totally cool! 

Until then!
Stuart

A pic I uploaded to the forum in 2017. I remember this! I just graduated highschool at the time. Totally crazy to still see it on the website in the gallery.

** brushes off the dust settled on his Forum account ***
 
Hi there guys,
 
It's been a long while. 
 
My name is Stuart and Ahoyworld was my life for 2 straight years before my uni. I remember the great times this community gave me almost every day playing EU3 and later AWE. It was amazing. Being known as a horrible shot I almost always flew transport and to this day it remains one of my fondest memories, shuttling troops to and from as Vortex 1 or 2 and later Angel 1 and 2. I remember that flying formation as two aircraft was the most rewarding and fun thing to do at the time. 

Well, with my uni starting I had to sadly take a step back from Arma as a whole and while I still played games, I never had the time to dedicate and come back. Until now. 
While the community seems to have evolved and had many ups and downs (atleast from what I could see by every so often stalking the forums) I am so happy to still see it around 6 years after I joined. (Atleast thats what my TS account is claiming, (22/01/2015) baby!). 

Eventhough I do not expect to experience the same gameplay I had back then, I am happy to be able to dedicate atleast some time back to Arma and there is no other community I feel I could be happier joining again. 
 
So hello everyone, new and old. I hope I can come chat with you on TS and maybe even see you around on the battlefield. The constant missions running currently seem totally cool! 

Until then!
Stuart

A pic I uploaded to the forum in 2017. I remember this! I just graduated highschool at the time. Totally crazy to still see it on the website in the gallery.

Now this topic says AW and its future, that's fair enough to say but I'm not giving a hell about AW I mean the EU1 players are going to be none the wiser about this its like what 50-60 people on at a time. (Don't give me an exact number) 
 
Its EU3(AWE) that all of you should be worried about. Most of the old player (Best players) have left AND NO ONE HAS A FUCKING CLUE WHY THEY ARE LEAVING? Argh.. 
 
I'd fucking stab you.. POINTLESS? HOW. Like I just said Most of the player who have been here for a while are leaving. Its not "Pointless" we tired doing something AND DON'T ANYONE SAY WE DIDN'T FUCKING TRY. But like I say to a good friend of mine about this. "We can scream and shout as much as we want. Nothing is going to fucking change."
 
 
 Well that's a faded out rule. AW is a fucking awesome a community well. Was a awesome community (I'm talking about the EU3/AWE side here) 
 
 
About flaming someone No. Of course not IF MOST ADMINS ARE POINTING AT ONE GUY WHAT DOSE THAT TELL YOU? ARE YOU BLIND? Wait. I forgot. Both you and Noah only see Rules. That's all you see isn't it? 
 
 
At the end of the day to make things easier for AW in general. I would start thinking about changing EU3 ASAP or pains me to say this: Take the fucker down and start from scratch. Now if you wanna quote every single fucking thing I just said please be my guest. 
 

I personally think it's time to put another training night together. An evening where we can all practice, and people can get the help they need. I don't think this should be overly specific either.
A group of people who're experienced and willing to help with whatever people need help with.
 
As a veteran I'd like to think I know most of what there is to know, at least to a basic extent. I might not know the intricacies of everything but I'd like to think I know enough about most things to be competent at them - and that's knowledge I think many of us hold and would like to pass on to streamline everyone's experience, as well as make it more enjoyable.
 
 

Let it be noted I fervently dislike writing things like this, but as a player and more specifically a veteran, I feel obligated to do so. 
 
Over the past couple months, I have seen a drastic decrease in organization and coherence on Enhanced due to an influx of newcomers. While, for the first couple weeks, becoming acquainted with the learning curve is to be expected, it is wholly ridiculous for this process to go on for months at a time. Additionally, with the typical process of "learning in the field" rather than through an official training night or a personal training session, vital concepts are being missed, ranging from improper radio use to failing to understand the medical system. Most importantly though, a sense of obeying the command structure is generally left out. 
 
I would highly recommend new players be required to attend a training night, or a personal session scheduled with an official Enhanced representative (mods, maybe Spartans and veterans) before being permitted to equip any roles that require a somewhat advanced knowledge of the systems in play on the server. How would this be enforced? That's a good question that I don't have an answer for. But is it becoming more and more necessary? Without a doubt, yes. I would be more than willing to volunteer any time I have to help with this process if need be. 
 
So that covers my little rant about player competence, now let's discuss a case of pilot competence that happened today (20/7/17) on the server. Names will be excluded for privacy.
 
Most pilots are extremely good at what they do, and I applaud them for the good experiences they help foster on the server. And I do not intend for the following to apply to them. Some, however, desperately need to be dealt with. Today, a player joined while I was piloting. Including him, there were two others on the server. He took the copilot slot. I immediately warned him that he was not allowed to be there; he needed to slot to Alpha. It took up to my fourth warning before he obliged and switched. In that time I was giving him warnings, he went over to the heli maintenance, spawned a helicopter (did not know what it was at the time), hopped in, and nearly took off. Carrying the single Alpha member in my helicopter (I assume the copilot was waiting for his reslot timer to end), I dropped him off to the AO and cleared a majority of the hostiles. After being shot down by a BMP, I disconnected. 
 
After leaving the server for roughly an hour, I came back and slotted up as an Alpha member. The copilot had switched to Alpha, then back to Vortex when I left. Upon reentering the AO, the pilot flew dangerously high and used autohover for landing, resulting in a nearly-shot-down situation. Upon landing, he continued to sit there for about 10 seconds, before turning his engine off entirely to communicate with Alpha Lead. He did return to base, but not before almost getting shot down again by the BMP due to his slow speed and high flight. Having to attempt landing three times (with that BMP still on him), he repeated this process while bringing in the FSG team. 
 
While he was making his trips, I notice something:
 
 
An Apache crash. That unknown helicopter he spawned was a two-seater Apache. During the time I was offline, he one-manned it, and proceeded to fly it into the AO and crash it. 
 
This was a "set up a comms tower" mission, so once Alpha and Nomad cleared the AO, he began to fly the crate in. Upon entering the vicinity, he was shot down by a BMP due to his once again linear path and slow speed. At that time, he disconnected.
 
My point here is that:
 
People should know the command structure, and know to obey the slotting rules. People, especially pilots and other specialty slots, should know proper conduct on the server. This is not a training server. You should know how to fly properly before touching these more advanced, modded models.   
-----
 
Once again, I would be more than willing to volunteer to help with training nights to help resolve these issues. Anything I can do to help I'm happy to. I had to put this rant/report out here, not because I wanted to, but because I felt responsible as a person who has a duty to the server and its population to obey the rules and make sure they're followed by others. The things above are beyond unacceptable, and need to be dealt with. 

For those of you interested in learning how to fly in the advanced flight model, I've written some notes below and made a short demonstration video to show you some of the stuff I'm talking about. It's a steep learning curve but it's also incredibly rewarding. Arma 3's advanced flight model offers probably the best simulation I've found so far of actual rotor-wing flight, and while it isn't quite the real thing, it gets stuff right that other simulators don't.
 
For those of you that are completely new to the advanced flight model, the key difference is that the main rotor now generates torque. The torque of the main rotor causes the helicopter to spin in the same direction, and if you want to fly in a straight line, you have to cancel out the induced rotation (hence why the tail rotor is called the "anti-torque" rotor).
 
To avoid confusion below, I will refer to "throttle" and "power" as "collective". But collective and throttle aren't actually the same thing -
Collective is a flight control that adjusts the angle of the main rotor to generate lift, also increasing aerodynamic drag and therefore reducing rotor speed, or RPM. Throttle is the main engine power and affects rotor RPM.  
In old helicopters, you'd have to carefully adjust the throttle to match the collective's setting so that the rotor RPM didn't reach dangerously low or high levels. However, in modern helicopters (and in Arma helicopters), you don't control the throttle. You control the collective and a governor automatically adjusts the throttle to maintain an appropriate rotor RPM.
 
Before venturing into the advanced flight model any deeper, I would suggest you get yourself a set of flight controls - some sort of analogue throttle control, a joystick and generic rudder pedals. It is possible to fly in the AFM with mouse & keyboard but the learning curve is much steeper, your movements will be sloppy and you'll find that building muscle memory takes weeks and months rather than days.
 
Your first challenges are going to be maintaining a hover, navigating taxiways and flying straight and level. All of these rely on building muscle memory with your feet, allowing you to correct the helicopter's axial rotation with an appropriate level of sensitivity in the anti-torque rotor. Note that, if you increase collective, the torque generated by the main rotor increases - so you have to apply more corrective pedal at a high collective than you would at a lower collective. In the video at the end of this post, look at how much the helicopter banks when flying straight and level, and compare that to how much the helicopter banks when taking off with full collective. The banking in this case is the amount of correction needed to counter the main rotor's torque.
 
Don't worry about landing until you've mastered the more basic flight controls. If you learn the basics first then landing will become much easier.
 
When conducting a landing in the AFM, it's much the same as in the standard flight model - drop collective, nose up, bleed off speed, gently touch the ground. But there's some further complications...
Ground Effect. This occurs when you're very low to the ground - the main rotor creates a bouncy cushion of air between the ground and the main rotor, as the air being thrust into the ground doesn't have anywhere to go. Ground Effect is actually your friend most of the time, it allows you to take off with less throttle and slightly cushions your landing at the critical point just before you touch down. But if you don't remember to take it into account, it'll be your worst enemy. Vortex Ring State (VRS). VRS occurs when you descend in a straight line without any lateral speed. The rotors descend into their own turbulent air and struggle to generate lift. The worst part of VRS is that the instinctive reaction is to increase collective, but this actually makes the situation worse (exact results depending on power-weight ratio). A helicopter in VRS will experience pronounced wobbling (like a magnitude 6 earthquake) and will move very unpredictably. To get out of VRS, you need to drop collective and nose forward to get out of the turbulent air. You'd better hope you're more than 30ft above the ground if this happens!  
And here's the video - some demonstrations and some useful knowledge to have.
 
Video Bookmarks:
Rotor RPM - 0:26 Vortex Ring State -  2:12. VRS looks different in vanilla Arma, ACE must be doing something here. Autorotation - 4:12 Ground Effect - 5:31 Traffic Pattern - 6:49 Free Flight - 12:15  
 
 

Sure, I am totally on your side that it could work again but the community seems to be pretty much casual by now wich just brings all these problems to the table and probably it wasn´t that much of a casual community back in the days you are talking about but instead a community looking for something MilSim-ish with a little bit more relaxed mentality.
 
 
You can...apply administrative sanctions(warn/kick/ban) to people doing dumb things like that.

This thread is going off the rails, and here we are calling each other out on everything they ever did. Id recommend closing it.
I could say i saw quite a few of members/vet's/spartans/ambassadors/admins/ etc. say, do,  stupid stuff/disregard the rules etc., often with a reason, often not, yep, we all do it every now and then (recalling my stay in the community some year ago), and i have done quite a lot of that myself, I've learnt a little. In the end, it's a game, and yes i understand caring, discussing and enforcing the rules, but lets leave it a discussion please, because what this thread is becoming now is a war of "who has done more stupid shit" and how obviously everybody dislikes that. 

I may not agree with all the rules and their enforcement, but at the same time, i understand them & the thinking behind them, and well, if i can't change them, i try not to break them more than twice a day. Also, im sure that the ahoy-world staff knows about what happened/happens and deals with it, we don't need to all be judges of that and express our dislike/hatred/spite in a forum thread, yes he broke the rules, yes there is a longer story behind it, and yes Ahoy dealt with it, really, it's that simple.
But, as we all know, we aren't going anywhere with what is happening now, and id just like to ask everybody, to, please not hate each-other too hard, and if you really wan't to, at least do it in a fight-ring team-speak channel, in the end, it's just a game.
Next time file a report and get on.

Cheers Miczils
I should probably start counting dislikes^^

hm.. you mean your joining in on this weekends Zeus missions?
 
Well, I am not quite sure how you want to be capturing footage outside of your gameplay. During these missions you will be of course playing in a team and wont really have time to be running around playing War Photographer.
If you are recording (which is great. You can often capture unique moments during playing) stick to first person as much as possible, it just looks better in 90% of the time. The back of a virtual mans head isn't to interesting and ruins any cinematic shot. 
Graphics wise you need to just test it out. In my opinion you can't rely on good hardware for having great graphics and FPS on AWE. Just try AWE out during normal hours and see how far you can push your machine. 
I am not too sure about TS. I believe NVIDIA Shadowplay -should- record the TS with it but better you test it out! While in TS I believe you can set yourself a "Recording" Status but I would have to check. If so, its good to let everyone in your channel know they are being recorded
 
Tips during the gamenight? hm...
I'd say do anything that dosen't harm the mission. Don't go taking pics during a gunfight while your teammates are engaging 6 Infantry Squads and a BTR all while being down to their last mags.
I think a good time to go picture hunting is probably during Infantry downtimes. Helorides, FOB time, anything where you are ordered to lower your guard or are waiting around. Then you can go looking for nice snapshots of scenery or let your Teammates pose!
 
Hope this is the answer you were looking for. 
 
Cheers,
Stuart
 
EDIT: No sadly there is only a Streaming Server Group you can set yourself too. So maybe just put [RECORDING] or similar behind your name while in TS
 
 

Hello,
Can't help you with the cinematography but the TS is ts.ahoyworld.net
 
-Fabs

I'm already crunching ideas for GN's where a decent FOB is justified. It's a difficult dynamic to implement without causing a major stall in gameplay when the FOB needs to be set-up. I think only a missions with a strong background story would really justify a FOB.
 

I thought the FOB yesterday was great. It just cut down time. It was also more fun, managing supplies. I had to watch out not to fire away a million bullets each mission because I knew I wasn't returning to base. We drove about a minute to FOB, rearmed and patched up for 5min and then were off again. That was just great!
 
Only issue I had and it might have been only me was the lag. I had real bad FPS at times. Might have just been the amount of players on one spot engaging targets all at once though.

I've long held that Logi is an unnecessary addition to Gauntlet. The spawn base is your FOB and no map is large enough that being forced to return is an issue.
 
Of course momentum could be better kept up in Gauntlet, but that's fixable by packing rearm into Vortex or into convoy vehicles.
 
Few tasks in Gauntlet involve defense in any meaningful way.

Some backstory on this, as I realize I just kind of dropped this functionality into Gauntlet without really explaining it. To be honest I don't see the Logi structures functionality as working well with Gauntlet, rather it would be better for a game night scenario.  But since it's hard to test how it works and fix / improve upon stuff without it being in the common mission, I elected to put it into Gauntlet and see how it works.
 
I agree, Fallujah is probably too small a map to really need a FOB, but I liked what I was seeing there.  Unfortunately I was just getting communications all over the place and wanted to keep the mission moving forward: I really needed to be Platoon Commander in order to have a better top-down view. But also unfortunately, I had to leave right as things were getting interesting.
 
I did have a couple of realizations, though.  The first is that the dynamic of having to leave the red circle marking the AO in order to advance the next mission is antithetical to the FOB setup I was going for, and frankly, there's no need for it in the modern Gauntlet code (its original purpose was to get players to leave the general area of operations so that dead enemy bodies could be cleaned up "quietly" - ie., the players do not see the bodies disappear).  I think I'll just move it towards a timer that spawns a new mission some random time after the previous mission has been completed.
 
The next is that I'm going to develop another mission parameter to filter out missions that require the players to RTB. For example, missions which require you to bring something back to base or take something from base to somewhere else on the map. This should produce an ability to string together missions that will keep players out in the field.
 
 
Disappointingly, thin objects will not stop AI from walking through them: only H-Barriers will do that. I don't think even the fences will stop AI (although the razorwire barriers might).
 
 
It's not intuitive, I know, but what it does is it rotates the structure to face the direction that you're facing. So if you're facing north, it sets the object's direction to 0 degrees. If you're facing south, it sets it to 180 degrees. I initially tried "rotate left" and "rotate right" but after three turns the structure would disappear!
 
 
The problem is that the structures aren't consistent in terms of how they spawn: some face the way you'd want them to, others face opposite to that. So if I rotate the H-Barrier walls 180 degrees, the other structures are now facing the wrong way, and I don't actually want to build in too much exception coding to specify which objects should spawn which way. If you spawn the structure, face south, and then set rotation, it should do what you want.  I'll look into a better way of handling this, but that's the way to do it for now.
 
 
I thought it was interesting that ambient targetted the FOB as it did: that definitely kept players on their toes.
 
 
I do like the idea of this but there are all sorts of issues spawning a composition of buildings. What happens if you try to spawn it on a steep gradient, or if there are trees and buildings around... part of the reason the FOB truck never worked reliably was that it needed a 20m clear, flat radius to deploy on, so that structures wouldn't clip / get destroyed / destroy other things. Plus what happens if you spawn a composition and someone is standing right where an H-Barrier deploys? At least in the minecraft method there is much greater fidelity in deploying the structures where they make sense. The individual structures only exist on the client's computer while they're being deployed so they don't kill/wound players while you are placing them.
 
 

Here's a quick push to remind everyone that there's a training session scheduled for this evening, 1830 UTC / 1930 BST / 2030 CEST.
 
We'd love to see you all attend. There should be something to take home for everyone, at the very least you'll get to play a custom town-clearing scenario!

Thank you @Noah_Hero, I hope it works out as planned
 
Considering Sign-ups - the information will be detailed during this week so standby!

Nope didnt, I did though experience 0 lag playing Takistan yesterday.
 

Well it's not like you die instantly. You can easily just be unconscious from pain. It's just the period of you having heart failure which is disabled for reasons stated above. 
 
Just yesterday a shell struck about 2m next to me and I got blown away. I was lying there unconscious for about 4 or 5 min. Honestly, I don't think a human being should be able to survive anything more then that. If a medic would have revived me  and patched me up (which he could completely, you can do a good two dozen wounds in 2 min if you know what to do) I would be fully combat effective again which is unrealistic and that's using our current system. 
 
In RL (and I am guessing here), I might have survived being blown to shreds, but I would have had to been stretchered out and medevaced ASAP. Being up and gunning again within 10min of treatment is a little silly. This would be possible with the "insta-death" disabled.
 

Well it's not like you die instantly. You can easily just be unconscious from pain. It's just the period of you having heart failure which is disabled for reasons stated above. 
 
Just yesterday a shell struck about 2m next to me and I got blown away. I was lying there unconscious for about 4 or 5 min. Honestly, I don't think a human being should be able to survive anything more then that. If a medic would have revived me  and patched me up (which he could completely, you can do a good two dozen wounds in 2 min if you know what to do) I would be fully combat effective again which is unrealistic and that's using our current system. 
 
In RL (and I am guessing here), I might have survived being blown to shreds, but I would have had to been stretchered out and medevaced ASAP. Being up and gunning again within 10min of treatment is a little silly. This would be possible with the "insta-death" disabled.
 

did restarting your router have an effect?
 

Hi
 
Have you considered installing ARMA on a separate SSD?
I will be doing this this weekend. , Gumpff on the net says it should help ARMA run much smoother
 
Gringo

Very good than I can help you further with troubleshooting:
 
Type in your browser "fritz.box" that should lead you to a site where you can make a lot of adjustement on ports/priorisation/etc also there you can check your data-transmission.
 
Here a few troubleshooting possibilities:
First of you will want to go to Internet->DSL-Informationen (buttons on the left side of the page). Then you will want to click on a button on the top that says DSL. That should lead you to a site where you can see what your DSL speed actually is. What values do you have in the first two lines (Datenrate Max and Datenrate Min)? (BTW in the two lines below is shown what you should get/for what you pay for. If the values of how many kbit/s you get are a lot lesser than the ones you are paying for it might be a good idea to call your provider and ask for a lower price.)
 
If you are playing via WLAN you will also want to go to  WLAN->Funkkanal and check there how many other signals are on the same channel as your one. If you see a channel that offers less signal interupption change your channel to that one (probably 13 will be the best channel because all Fritz-Boxes only set their channel between 1 and 11 by default what means that only users with a little bit more experience are using 12 and 13 and 13 is the most farest channel to the default ones what means that there is probably the lowest interruption by signals that use nearby channels.)

hmm that is definitly a lot and the number is static because it is the max you received. And this high value will most definitly just be there since the Glasfibre has been deployed what than means that the cable is also good. So it´ll probably not be your connection.

Perhaps an outdated approach, but there used to be an issue overwhelming your CPU with audio sources demanding too many cycles.
 
Check your audio settings and look for the number of allowed sound sources. Try decreasing your value (96 by default) to 32 for testing purposes, or go straight to the extreme and run Arma using the -nosound parameter. See if that has any results.

You say it worked on and off for a while before completely blowing. To me it sounds like something cooked through. Is it the power cable to the GPU maybe?