wess24m

BRILLIANT!!

Ya i found where it gives the options in the DSMS for the HOF settings of the CBU-97/105, I guess I could try to change them all to 500 and see if it works. Hopefully one day, we can get a implemented data cartridge.

That and the fact I only play multiplayer is the reason i'm stuck at the most current iteration. Although i'm looking forward to 1.2.4, I'm dreading what it's going to break.

I agree. What you built should easily run DCS. I'm assuming that the recommended requirement are what they thought would run DCS well without all the bugs that are plaguing it. I'm by no means defending ED, I realize that they are a small team but they should prioritize the playability bugs first before devoting manpower to additions to the sim. On the other hand I'm not going to "bad mouth" ED because some of the mods/ED testers/ED team members overzealously jump the gun and try to shift blame to the users. I'm avoiding all that drama and just wanted some feedback for an issue I could possibly fix myself.

I agree, I was rebutting your claim that everybody has this issue. Yes it's a bug, yes we shouldn't have to find workarounds for a game we paid for, but it is what it is and until somebody corrects the issue we're stuck if you want to play the sim. Building a high end gaming computer has many other side benefits though, I didn't just build my rig with this game in mind. I also do image rendering and HD video editing which also requires a powerful computer. Fixing (some of) the issues with DCS was the real side benefit. In the long run spending 2-3k building a computer is relative to your hobby needs, if i'm spending most of my time on a pc then it behooves me to have good equipment. I'm agreeing with you to a point. This is off topic and I really am just trying to find a way to fix something that needs fixing. I've been playing this sim since the day it came out in beta and once you've had to go in and change CBU settings a few thousand times for something that should be set low by default it gets old.

I never said there wasn't bugs, what I'm telling you is get a better setup and a lot of the performance bugs are mitigated.

Like I said not everybody has this issue. I'm running a i7-3970X overclocked to 5 ghz. I still drop down to 30 fps with CBU 87, but that's the only slowdown I get. It is something Ed needs to fix but if you had a better setup it would make it MUCH less noticeable.

Not everybody has issues with 97/105. I get zero frame drop when using 97/105 or being around somebody else dropping them. They are effective at destroying all tanks/Vehicles. Maybe invest in a better processor and a SSD.

So back on topic, nobody knows where to change the defaults? In all reality the HOF is set on the ground, so there would be no changing it on the fly anyways.

get your lat long from your position on the f10 map and input them i to the cdu alignment page during first alignment the cdu is using lat longs from your virtual data cartridge.

if its modeled correctly, the reason why you have errors in the navigation is because during initial cdu alignment its using nav location from your virtual data cartridge. you can manually input LL from the f10 map for your correct location.

Exactly, I've looked through all the DSMS,weapons,cockpit lau files and can't find anything. Maybe i'm just missing something obvious.

Default settings. As in when you load them onto the aircraft. On that subject, you might as well set them to 500 feet because they don't model real skeet height dependant targeting, pretty much eliminates any need to compensate for wind when set at 500.

I target pod view of both enemy and friendly (for when you're playing red side) vehicles and aircraft. Anything for the blackshark. I read awhile back that somebody was making an interactive app, say you have an engine out it would popup with engine out procedures (even though we should know these front and back). A movable and zoomable map, with frequencies (both comms and nav). A practical way to export your TGP/shkall to an ipad. A way to pre-program your CDU. I've yet to see an app for DCS with any of those features.

Anybody know which .lua file to edit to change the default HOF settings in the DSMS? I'd like to change it to a usable level.

Point proven I guess.

Thx for the write up but you do realize this is a video game and not real life correct? If i'm playing a video game, I'm not getting shot down, and my bombs fall on target then mission accomplished. I'm all for doing things the correct way but when people start berating another person because they haven't been flying as long or have real world experience they need to take a breather. In my posts I'm telling them to get the basics down before killing themselves and getting frustrated because they can't get these deliveries correct the first couple times. I'm sure these newer people would be more receptive to the information you've provided if you didn't come off with such a condescending attitude towards them.

Don't worry about that thing, just try to maintain a valid solution without diving into the ground. I can't think of a time where you absolutely have to have a certain amount of fall time.

Again, take small things like that with a grain of salt. 33 feet isn't going to make or break your run in, you can also make corrections while running in to correct any base altitude failed setup. As you can see in my video all my runs hit targets despite being exactly at this speed or that altitude. The TAD (really all the aircrafts systems) only help you be more effective. I've been flying this sim since the day it came out, matter of fact I took a week off of work to get started. Watch lots of YouTube videos, Eddis are good and will establish good habits right from the start. Just relax and spend some time at the training range, try different things, see what works so what doesn't. Have fun.

I do have a rudder but its bad form to use it for lateral correction for gun runs and bombing. When you crab the aircraft not only does it effect your pitot tube flow which in turn effects your airspeed reading (if they ever implement that real world condition) which in turn would effect your ballistic computer (because of the erroneous airspeed reading), it also doesn't effect the path of the aircraft to a substantial degree, you're just going through at the air sideway on the same flight path, also it doesn't/didn't effect your accuracy. If you notice my first run was spot on where I was aiming for, the 2nd and 3rd runs were early and off. The 2nd was because I released too early, the 3rd was because my alignment was off. I was showing mainly that you can run in close to parameters and still get both, bombs on target and a valid solution cue. Like I say, my methods are effective on getting bombs on target and maintaining safely of the aircraft. I realize this is a game but I treat it the same as when I'm flying IRL. Getting shot down is the ultimate immersion killer for me so I play with making it home in mind, you can both fly aggressively,safely and still be effective.

Both are possible, make sure that if you're dropping in CCIP that you set your min alt in your profile to above the HOF of your CBU. Of course CBU 105/103 should be dropped in CCRP because of having to set the ins/GPS information prior to release.

You could always get as close to the location on your TAD map as you can (IE the target was by a road intersection) and place a mark point. The mark point would then use known Terrain elevation and incorporate that into the HOT on your bombing solution. If your off by a couple feet it's not going to destroy your solution. That and the limited blast damage modeled will help.

I don't think it's so far off as to be disregarded. The times I've seen it give the invalid release cue it's working as intended. For others that don't know, the altitude staple is calculated upon the aircraft continuing on the same flight path as indicated at that specific instance. So if you don't alter your flight path (when its showing your staple below your target) you will exceed the minimum safe altitude input into the IFFCC. I use it and as long as you're flying a correct delivery path then you won't get an invalid release cue.

Here's my attempt at Bills track. I delivered from the target altitude first then 2 more passes at different altitude and positions (as you would in the wild). Notice that my solution is valid through the entire run in and I only briefly have an invalid X AFTER the bombs were off on the first pass. I was less concerned about speed and keeping things exactly right as far as the given values, and concentrated at getting the bombs on target and not putting my aircraft at risk by dropping below the safe altitude or needlessly exposing myself to the enemy. While these guides are great, they aren't the end all be all. Be concerned with you and your aircraft's safety as well as your team, try to get bombs on target but (as Eddie said previously) don't be afraid to abort if things aren't looking right, aborting is much better then pushing a bad situation. Sorry for the split screen, I have exported MFCD's and I don't normally make videos.

You ask a question about something covered in the manual, then say you've read the manual several times and are tired of being where to find the answers. If you want to learn you need to take a little bit of responsibility to be self motivated and find the answers and not have to be spoon fed. I'm trying to help you guys, but when I read this kind of response it makes me want to take the stance of most the people here and tell you to figure it out on your own. That quote was directly out of the manual you say you've read. It was also a direct answer to your question, from the manual. I'll be posting a video in a minute showing you guys that I flew the trk file and made 3 successful run's on the target, from varying altitudes and speeds all while maintaining a valid ballistic solution cue (no x through the retical). As I said get to where you can do a straight on dive bomb while not burying your escape staple in the ground, then add complications (the turn in) to the equation.