Jump to content
COMBATSIM Forum

TAW 2.0 Known Issues and Bug Reports


Home Fries
 Share

Recommended Posts

Have 'Faith' Mike!...their upgrading my local exchange at the moment, it will all come good you'll see.....if not then i'll take your advice, i've had no prob's for 3 years!, its only since November it went down hill, BT isn't that good either!, just ask the guy from my work!, he's connected to same exchange as me only he's with BT, and got same problem, so i think that's where the problem lies. ;)

Link to comment
Share on other sites

  • Replies 537
  • Created
  • Last Reply

Top Posters In This Topic

Okay, I just flew a BAI mission where my flight was tasked with taking out surface mobile anti-aircraft. I used the auto-pilot in WP mode all the way to the target (WP-4) and, once again, I had to manually advance after overflying WP-3. This indicated that a non-escort flight mission on auto-pilot still experienced the WP-3 hangup. It's not that big of a deal, but I thought I'd mention the observation.

Link to comment
Share on other sites

Cmdr Sweeper, wouldn't you want the Wild Weasel guys to go in ahead of you to suppress threats in the target area rather than orbiting at a hold-short waypoint? The Wild Weasel and CAP guys did not loiter at the waypoint, but went in with me. I suppose they might have loitered had I not manually advanced the WP as soon as I saw it did not auto-advance. Definitely not a show stopper, but I don't recall seeing anything in the manual about this feature.

Mike, the AP MFD simply labeled WP-3 as "pass", like the others along the way to the target.

Addendum: Just flew another BAI strike using auto-pilot in WP mode and everything advanced properly. Seems to be a hit and miss issue.

Link to comment
Share on other sites

Twice I've been handed a BAI strike originating at Mekele airbase and twice I've flown the profile, returning to the designated base only to be awarded a "mission failed". One of the failures was for not returning to Mekele even though the event map clearly showed the mission had originated and terminated at the designated airfield. I presume this is a bug, albeit an annoying one as most bugs are.

Having read the post about how to target stationary items, I followed the procedures and slammed everything in the vicinity but was not credited with a mission success. I saw the red triangle on my attack MFD and on the Situation MFD, but saw no such marking on the actual target as depicted in the post. Again, this is the same mission I've failed twice as mentioned above, so maybe it's another aspect of a buggy mission.

Link to comment
Share on other sites

We can actually go in and have a look at mission objectives in the structure of missions. Its all to do with the .cdl, .kdl, .mdl, .pdl, etc files. I'm no expert but the veterans here tend to focus on problems with th MP missions as Eagle was doing yesterday with some MP campaign missions developed by Hawkx.

In regard to the "locked WP points" I'm not sure. I (we) constantly use autopilot in MP (the WP selection all controlled by the Lead, its the only control), and we are in and out of autopilot and its an individuals preference as to whether he uses the autopilot WP's. Yesterday three of us flew in very close, scary close, :superscare: "fingertips formation" with WP autopilot, but even, when in such close formation, planes can tend to drift together if line abreast. (They all want the same spot at the WP.)

I hate to push this, but to really come to grips with TAW2.0 you need to fly MP with the veterans: HF, Neph, Hawkx, Eagle are the current regular flyer's. Not me. I'm there learning and to be shouted at .... ;) I am still on the learning curve. If you want to get the basics of taxiing, take-off, etc, in MP, there are one with one sessions available to cover the same. (I current have instructor/trainee sessions running with Iceman. Mind you its a bit like the blind leading the blind, :lol: but that how we both learn). It doesn't matter how good a SP pilot you are, MP is different. The challenges are different and so much better than in SP. We really only fly SP if we can't get a MP session going. That's why we want you to join us. Selfish aren't we ..... ;) My advice: get your systems running so as MP is available and join us half hour before the regular flyins for questions and answer; or get organized to fly one with one to do the basics. Then at least you can confidently get into the air. It only takes a PM. :thumbsup:

EDIT: Mind you what you are doing together (that is Red and Spectra) is just great. :thumbsup: Its a great way to learn. We will watch with interest.

Edited by Wombat1940
Link to comment
Share on other sites

Thanks, Wombat, I really am working toward the proficiency I figure I'll need to jump into MP. I flew Janes WWII Fighters and IL-2 in MP for many years and always found it to be more dynamic and satisfying than SP even though DID's offline missions are superior to either of the former sims, IMHO. Still, there's a bit more systems management to be mastered in an F-22 than a WWII recip. I'm getting there and hope to join you guys before long.

Link to comment
Share on other sites

Hi, and good afternoon gents.

Everything was working well until yesterday, when I clicked on the "Customisations" button in the TAW launcher, which gave me the "mscomctl.ocx missing" message. Since then, I've had no sound in the game. I don't mean no speech, I mean absolutely nothing. Not even the click when you click a button. I tried reinstalling the game, reinstalled Truespeech codecs, copied the aforementioned file to the "system32" directory and registered it, but still I've had no luck. I'm using Windows 7 Professional Edition x64. Any ideas? Also, for some reason, running the game with compatibility mode set to "Win XP SP2" creates graphical artifacts (I use the original glide), and I'm better off using no compatibility.

Link to comment
Share on other sites

Martinus,

Sorry to hear about your difficulties. I will say, however, that the TAW Launcher and the TAW game are completely unrelated when it comes to sound (with possible exception of midi volume), so are you having any sound issues with other programs?

The troubleshooting steps you took would have been my recommendations, so I'm at a loss. I use Win7 x64 as well. BTW interesting about the XP compatibility causing graphical artifacts. Which glide wrapper are you using? I may remove the compatibility default in future builds.

Link to comment
Share on other sites

Thanks for the quick response, mate.

Well, right now I'm like :blink:

I changed the exe to "Direct3D 800*600" and opened the game, and all sounds were back. Also, I noticed that even without compatibility mode, I see graphical artifacts when I switch to "Movable External" or "Flyby" views when using Glide. Actually, those artifacts are more than simply "artifacts"; they made my graphics card stop and the game froze. The same thing happened every time I tested that. And as for other programs, I have no sound problems. Given that, I now don't really know if it was the compatibility mode that made those artifacts appear, I'm gonna have to check it with D3D. Most probably, I've got problems with the Glide wrapper.

By the way, when I choose "Direct3D 1024*768", the game loads and everything seems right, but when I choose a mission, the game crashes and gives me a message saying "Direct3D 1024*768 unsupported by hardware." Why is that? I have a laptop with an NVIDIA graphics card.

Thanks in advance. ;)

Link to comment
Share on other sites

Glad to hear D3D worked for you. At least that rules out driver issues.

I do have a few questions:

  1. What is the supported resolution of your laptop screen? Is it 720p (which would rule out a 1024x768 resolution)?
  2. Which nVidia card do you have on your LT (e.g. 7050M)?
  3. Which Glide Wrapper are you using? If dgVoodoo, are you using the D3D7 or D3D9 renderer?

Link to comment
Share on other sites

Interesting. You answered all of the questions "correctly". Can you select 1024x768 in your windows resolution selector? I really don't think this is the issue (otherwise the laptop would have compatibility issues for a lot of programs; not smart design), but it's the only thing I can think to check now.

The only other thing I can think of: when you went into the 1024 game, did you do so from the configuration screen? If so, the program is set to 640x400, which could cause issues (it's set to 640x400 by design so you can go to the options screen without CTD). Likewise, if the game crashes when the demo starts, that's indicative of the same problem (i.e. not supporting 640x400).

Link to comment
Share on other sites

Yeah, one of the available resolutions is 1024*768. And you're right, that's not the problem. But about the second possible problem you mentioned... Actually, I just checked that. When I use the "Configure D3D 1024, everything works right (except smart views, which are actually supposed to crash the game with D3D). But if I use the "Update EXE" and then run the game from the launcher's main screen, I get CTDs. That's kinda strange.

Thank you very much for your help. Can you think of any reasons for Glide suddenly going crazy?

EDIT: Yeah, that's it. The hardware doesn't support 640*400. Thanks for the great support, man.

Link to comment
Share on other sites

When I use the "Configure D3D 1024, everything works right (except smart views, which are actually supposed to crash the game with D3D). But if I use the "Update EXE" and then run the game from the launcher's main screen, I get CTDs. That's kinda strange.

I agree. It should be the other way around. Because the 1024 resolution is a hex-edit to the did.dat, when you go to the Options screen with 1024x768 selected, you get a CTD. The way around that is the "Configure" button in the launcher, which sets the game.cfg to 640x400 before loading TAW. This way you can get to the options screen to make your choices, but shouldn't go into the game itself.

So you're getting CTDs when launching from the main launcher screen (i.e. clicking on the big F-22) that have nothing to do with the demo screen?

Thank you very much for your help. Can you think of any reasons for Glide suddenly going crazy?

I can't, but you may want to try nGlide. I use this on my laptop (nvidia 7050M) and get good results. If you don't want to do a full system install, I can post a link to a local (i.e. only for that folder) version of nGlide which I will be putting into the next TAW release.

Link to comment
Share on other sites

I agree. It should be the other way around. Because the 1024 resolution is a hex-edit to the did.dat, when you go to the Options screen with 1024x768 selected, you get a CTD. The way around that is the "Configure" button in the launcher, which sets the game.cfg to 640x400 before loading TAW. This way you can get to the options screen to make your choices, but shouldn't go into the game itself.

So you're getting CTDs when launching from the main launcher screen (i.e. clicking on the big F-22) that have nothing to do with the demo screen?

No, I meant that when setting the game to D3D 1024, I should first launch the game using the "Configure" button, change the resolution in Options to 800*600, then I can also run the game from the big F-22 in the main launcher screen. Correct me if I'm wrong.

Also, running Demo gives me a CTD with D3D 1024 (EDIT: Or D3D 800*600. But that's supposed to happen I think, because the "Glide vs D3D" PDF lists that as an issue with D3D).

Link to comment
Share on other sites

No, I meant that when setting the game to D3D 1024, I should first launch the game using the "Configure" button, change the resolution in Options to 800*600, then I can also run the game from the big F-22 in the main launcher screen. Correct me if I'm wrong.

You're Wrong! :P

"Configure" is exactly for that: it tweaks the game.cfg to let you into the options menu without CTD. Once you make your choices in the options menu (don't touch resolution!), exit TAW. This will change the game.cfg back to 1024x768. Now you run TAW from the main screen to get 1024x768. This is explained further in the Manual Addendum.

Also, running Demo gives me a CTD with D3D 1024 (EDIT: Or D3D 800*600. But that's supposed to happen I think, because the "Glide vs D3D" PDF lists that as an issue with D3D).

You are correct! The Demo always runs in 640x400. The only way around this is to use a glide wrapper and upconvert the resolution to something supported by your hardware (e.g. 800x600).

Link to comment
Share on other sites

Well, looks like D3D 1024 isn't really supported by my hardware :D

I did what you said, and when I tried to run a mission, I got the above message. That's alright though, I can live with D3D 800*600. :D

Thanks for your responses, Home Fries.

As I think your earlier post said, you are running TAW2.0 on your laptop. I recon 800x600 would look just be fine (save for the map in the Sit. MFD of course). Unless your laptop has a 32" screen. ;)

21 to go, and counting ......

Link to comment
Share on other sites

Got CTD after all targets destroyed during Missle Evasion training mission in dgvoodoo Glide 800x600 16bit.

Program fault at 0x527C72, cleanup up and exiting!

00000595 0006FB90 00527C72 00250286

FFFFFF00 3E6FFFFF 00000008 FFFFFF00 00000004 00CEA070

00000023 00000023 0000003B 00000000 0000001B 00000023

version 5.191 by  on Nov 16 1998

EDIT: Never had CTD in Glide during this training mission before, never had CTD in Glide before!!, but what i did different was to launch all 14 AGM 65's at the 3 SAM's or however many SAM's their are?.....my thought is that the explosions of 14 65's happening seconds after each other caused the CTD??

Link to comment
Share on other sites

It's possible, redfalcon. Also, did you fly over/through any explosions at the time. That has been known to cause crashes, though primarily it is from gun/rocket use where you get much closer to the target.

Also, which glide wrapper are you using? I assume dgVoodoo since you said you're in 16 bit, but I want to be sure.

Link to comment
Share on other sites

It's possible, redfalcon. Also, did you fly over/through any explosions at the time. That has been known to cause crashes, though primarily it is from gun/rocket use where you get much closer to the target.

Also, which glide wrapper are you using? I assume dgVoodoo since you said you're in 16 bit, but I want to be sure.

No did not fly through explosions!...using dgVoodoo 800x600 16 bit, no guns fired.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • Create New...