Winston 60

In the Su-33 you ALWAYS get the CCIP pipper and bomb fall line immediately after selecting A/G mode and bombs. This is where the problem occurs for me, as you don't know on a bomb run in if it's going to give you the CCRP diamond or just release the bombs at your current CCIP aiming point when you press the trigger. I know it has to do with altitude, dive angle and distance to target, but it seems a crapshoot if: a. you get the diamond :dunno: or b. the bombs will just immediately drop. :thumbdown:

I'm glad to see people making skins for the new MiG-29S model. These will be great! I'm hoping someone will also do some German skins for the "S" for fictitious multiplayer use.

For me the AGM65-H is working properly in A/G mode. The weapon displays in the lower left of my HUD and the maverick camera comes on. Did you try a repair or remove mods?

OnlyforDCS... When you are ready for multiplayer, would you care to try a test flight with our small Squadron? We are in the USA pacific time zone and fly coop multiplayer missions against AI adversaries. This may be a great way to prepare you for bigger multiplayer stuff. PM me for more info if interested.

Tip: Clients who leave the server need to use "disconnect" and not "exit". Sometimes this causes problems.

I agree, the second sound canceling the first one is not good. It would be much better if the first sound played completely before playing the second one.

Mission 3 files have been updated. Repaired a few LSO bugs and made a few enhancements. Note that the Carriers LSO voice instructions are a work in progress. If you think you can save your landing after getting a "wave off" by all means go ahead and try. Changes: 1. Start on the Carrier. In multiplayer missions, plane 1 should always be on the Carrier deck along with any one of the other planes to start the mission. After spawning in, you may start engines but do not launch until you hear the voice briefing. Do not rearm, go with the provided loadout. 2. After the in-cockpit briefing, all planes have 5 minutes to get 2.3 km away from the carrier. In the 3 to 4 player multiplayer version it's important for the first two aircraft that takeoff circle the carrier at this distance while waiting for the rest of the flight to launch. On returning to the carrier, if you bolter or go around, make sure your next approach takes at least 3 minutes before lining up with the carrier again. These times are necessary to re-set the LSO speech. 3 to 4 player multiplayer version coming Mar. 3rd.

I ordered and paid for one of these on their website a few days ago. Are you saying they're going to inform me that these are actually not available? http://vkbcontrollers.com/?product=vkb-tm-warthogtm-adapter-for-gladiator-pro

Mission 3 uploaded, see the first post. Singleplayer (untested) and 2 player multiplayer versions added with the 3 to 4 player multiplayer version coming soon. Note: The Carrier LSO voice is a WIP. If you get a waveoff and think you can save your landing, by all means go ahead and try. Please report any bugs or problems here or critiques and criticisms, or ask a question if you are having trouble with any part of the mission. I also accept "Thank You's" and rep. The discussion here will determine how long I stick with this scenario before moving on to something else. Enjoy! and if you had something interesting happen, tell us about it here or post a screenshot. Or if you absolutely hated something, I'd like to hear what that was too!

For fictitious multiplayer use.

Some people have done similar to this for the new MiG-29A template but for the new M-29S template I'd like to see German M-29's with the dark radome, dark vert stab tips and two color paint. Kudos if you can do some like this.

Yes, would like to see this effect. Maybe also a "death sequence" where your in cockpit pilot's 1st person perspective gives you a slowly forced head moving down movement followed by a gradual blackout.

Careful of F keys that are trapped by TrackIR's (if you use it) default settings. For example F9 in DCS shows ships external view, but if F9 is trapped in TrackIR software the F9 key will not perform any function in DCS.

Last time I tried was a few months back. It's OK in a pleasure flight, maybe just cruising around solo or against just a few planes or targets, but in the heat of a large scale multiplayer session my FPS was down in the 20-30's from it's usual 50-60. My CPU is a 7 year old 1st gen intel i-7 and it's a bit slow compared to what most people run today.

Some good things in your list there. Naval engagements and graphics quality are primitive in DCS now. May I add that all ships should create a stern wake too instead of just a bow wake. Currently though, it's nice to see a Grisha shoot down Harpoon missiles with it's gatling guns. Ships do turn now, but not to bring their guns to bear. They turn to evade attack and how much they turn and evade depends on their set skill level.

Thanks razo+r, tried that once, they look great but too big a FPS hit on my older system. I can't wait until they optimize the code on the new clouds a bit more though. Maybe they're sneaking a bit of the new clouds in gradually as the ones in 1.5.6 differ oh so slightly from 1.5.5.

Our squadron noticed this too immediately upon updating to release version 1.5.6. It can be seen that the 1.5.6 clouds have been changed some, each cloud is now taller than before. I often use heavy and thick clouds in my missions and this is quite nasty to look at when it happens often due to the sheer number of clouds in the sky. As you approach the clouds they begin to swirl and rotate, then turn into streaky lines, then vanish! If you look behind you at some distance the cloud will pop back into view. I was surprised no one was reporting this! This is a nasty bug that has returned in 1.5.6 from a previous version awhile back. I've spoken to an ED representative and he says they know about this issue and are looking at it again. Maybe if enough users chime in here with their verification and say that this is an issue for them, Ed can bump it up to a higher level and get it fixed sooner? :thumbup:

Welcome to mission building Kaliphtan. It's best to post mission building questions in the "Mission Builders' Corner" topic above rather than here where most discussion is about "Missions and Campaigns". :smilewink:

Regular infantry have not been firing for quite some time. Use the "Paratrooper AKS" infantry instead. Whether they are spawned in or present from mission start, they are the only infantry that fire at the enemy.

I'm not finding a video review, but here's a written review and the IP did a pretty good job with his first impressions/review. http://nerdtechy.com/vkb-sim-gladiator-pro-joystick-review

Add some 'dead zone/null zone' to the center of your Track IR's axis'. This will keep your view from jumping around when you make very tiny head movements but you'll still have a full range of tracking when you move your head past this new small dead zone/null zone. This also negates the need to always having to re-center the Track IR. If you can't do this. let me know and I'll upload a pre-modified profile for you.

...and one for grip setup

Here ya go my friend, a video on cam/spring installation.

Just wanted to add that the engines startup-shutdown seems to be correctly implemented for L and R. Unlike the Su-25T which starts the right engine when the left engine start command is issued, the Su-33 starts up and shuts down the engines in the proper order. It's just the engine fire that is reported on the wrong sides.

There are many graphical issues in ver 1.5.x that are seen differently by some of the clients in a multiplayer environment. If a player is hosting the session on the same computer he's playing on, there's an even better chance to see something like this although the host of the game may see the gear and the other clients will not see the gear.