Which exe are you running? Try deleting the previous files and unzipping them again.

Are you using left or right ctrl for time acceleration?

Seems to be an issue with all debug versions that they can't do time accel.

It might be toggled off for debug versions. I'll check the next time I'm on.

Did you get the issue resolved for the rotors and weapons not showing?

I have not. I re-copied everything and replaced it again and still do not see my own rotors or weapons from within the cockpit. It said it replaced over 180-something items, so I think whatever was in what I downloaded is now in the correct spots. The updated files I've looked for with new modified dates also are showing those in the correct save spots.

You know you can disable/enable visible rotor in cockpit by keyboard?

Yes, I have it enabled and have tried toggling it and it's having no effect in the blackhawk cockpit. You can see the weapons and main rotor from the cockpit in the lastest version?

Edit: I have a theory as to why I might not be able to see it: cockpit detail is probably turned down. Does that normally remove rotors or weapons from being seen?

Another edit: Yep, that was it. Not sure if it ought to be that way, but cockpit detail is controlling whether you can see that other stuff in the blackhawk.

I fired up version 1.11.1 and tried it in the Hokum, and the weapons and rotors are removed if you reduce cockpit detail. And as those cockpits are the ones that all the newer ones are based on, then it seems to be expected behaviour.

Side note: Go fire up 1.11.1 to see how far this game has come.

1. pilots hand is still visible in widecockpit view.

2. Hellfires TOF is not displayed properly. In other helicopters the TOF number is decreased regularly, but in blackhawk the TOF starts higher than usual, decreases very quickly and the decreasing speed gets slower as the number is getting close to 0.

3. Im still getting CTD issue sometimes when entering any helicopter cockpits after I installed this MOD. this issue was not happening when I didnt install it. unfortunately the debug dont say anything useful. this is my debug log when I selected transfer mission and tried to enter comanche cockpit.

COMMON: Player Hijong park assigned to task Transfer @ 1144.70
Setting gunship to AIRCRAFT_RAH66_COMANCHE @ 1144.70
Assigning gunship to user: AIRCRAFT_RAH66_COMANCHE @ 1144.70
Setting gunship_entity (type = ENTITY_TYPE_HELICOPTER, index = 47672) @ 1144.70
DYNAMICS: initialising flight model @ 1144.70
DYNAMICS: added flight path data [60728.421875, 55499.347656] action ACTION_AUTOPILOT_NAVIGATING @ 1144.70
5 blade roots, 1 rotor shafts, 1 tail blades found @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_MAIN_ROTOR (0) at 0.431389, 0.837759, -5.744341 @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_MAIN_ROTOR (1) at -3.767050, -0.251686, 4.449860 @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_MAIN_ROTOR (2) at 3.064466, -0.305126, 4.949913 @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_MAIN_ROTOR (3) at 5.654980, 0.368167, -1.350250 @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_MAIN_ROTOR (4) at -5.405400, 0.456154, -2.173570 @ 1144.70
DYNAMICS: Found moving collision point DYNAMICS_COLLISION_POINT_TAIL_ROTOR (5) at 0.087500, -1.299500, -6.985600 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_STABILISER (0) at 0.000000, -1.400000, -8.519998 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_STABILISER (1) at 1.555431, 0.727792, -8.054033 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_STABILISER (2) at -1.286161, 0.727792, -8.029772 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_FUSELAGE (3) at 0.000000, -1.009965, -2.983675 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_FUSELAGE (4) at 0.000000, -2.288413, -2.322783 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_FUSELAGE (5) at 0.000000, -2.797625, 3.917794 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_FUSELAGE (6) at 0.206536, -0.670606, 2.726017 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_FUSELAGE (7) at -0.225434, -0.670606, 2.726017 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_ENGINE (8) at 0.902219, -0.896539, -0.567804 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_ENGINE (9) at -0.902219, -0.896539, -0.567804 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_NOSE_GUN (10) at 0.000001, -2.610000, 2.036323 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_AVIONICS (11) at 0.000000, -2.100000, 5.000001 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_AVIONICS (12) at 0.000000, 0.861449, 0.094839 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WHEEL (13) at 0.432845, -2.430323, 0.880043 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WHEEL (14) at 0.100000, -1.921493, -5.199246 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WHEEL (15) at -0.432845, -2.430323, 0.880043 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WING_TIP (16) at -0.317736, -2.422170, -0.384780 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WING_TIP (17) at 0.290826, -2.423769, -0.391143 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WING_TIP (18) at 2.330943, -1.593722, 0.000000 @ 1144.70
DYNAMICS: Found fixed collision point DYNAMICS_COLLISION_POINT_WING_TIP (19) at -2.330900, -1.593722, 0.000000 @ 1144.70
DYNAMICS: damage_percentage is 1.00 @ 1144.70
Load Comanche damage: 0 @ 1144.70
hud colour 2 9 @ 1144.70

Fixed in the latest update.



Is TOF the time to impact after launch?

I'll try and see what's causing this.



I think this might be related to the textures being used. The Blackhawk (and also the Viper and Kiowa) uses the Comanche textures for the MFDs to display. So it's maybe not initialising them properly when you switch cockpits. However, it's a bit of an edge case, as you normally wouldn't use cockpit switching in a campaign.

I know I'll be boring Do not hit me but still a lot of textures are the wrong size, and in my opinion that could be causing most of the ctd. I know it takes a lot of work but .... I had a lot of cases where the ctd was caused by the wrong textures.

Hey Messyhead,

What is involved in resizing the textures ? Is it something I could do for you if you sent me them ?

What software is required ?

I use Photoshop and Ansys Spaceclain regularly if that would be any use.

Cheers,

Andy

Polak has already sent me resized textures, but I've just not included them yet. I need to verify that they're all the right ones, as some were in png format as that's what the lightwave model used. So I need to update the models. I've just not done it yet as I was working on other things.

I was also hoping to try dds with mipmaps to see if it got rid of the shimmery effect. But I've also noticed that some of the original tga textures are tagged @1, @2 etc, so I think that might be for mip mapping, and I was going to try that too.

In term of software, I use photoshop too with the nvidia dds plugin

If you get a ctd due to textures, can you post it here with what you were doing, and the error so I can investigate it.

OMG i telling you about bad texture sizes for many years, from the first test release. you are still publishing new builds, and you are very surprised when people have an inexplicable ctd. I've reported a texture problem so many times that I can't count anymore.what's the point of reporting if you haven't fixed the most serious bugs for 10 years, and it generates many other problems?> You're a software tester, and that's what a tester does? You didn't do anything about it, and you don't. and knowing life, you will release the final version that will blow up the game, because it will be ctd. it doesn't make sense anymore, I give up, and I'm leaving this forum. btw your nickname fits you perfectly. bye.

You can f%#* off.

I tell you what, you go make a cockpit from scratch, code, texture it, fix the issues, have 2 kids, get married, change job 3 times, move house twice, and do a better job. Why the f&*# am I giving my own time, for free, for a game. I must be mad.

Maybe I'll just delete the thing once and for all and walk away.

p.s. have you offered to help with texturing before instead of just commenting?

This should free up some disk space, not to mention personal time.

#blamebanita

Hey Banita,

What's with all the negativity ? I thought we were all here to try and improve a game we love. I offered to help Messyhead without any knowledge of what was involved, why didn't you as someone who obviously has more of the required knowledge than me ?

The guy said he had the resized textures but had to check them. What is the problem ?

Messyhead,

Just ignore him. I've noticed a lot of his posts have been negative.

Don't destroy what you have obviously spend a lot of time ( and your own money) on because of one person.

I don't know what is involved in what you did, but I can (like many others) appreciate that it is a lot of hard and frustrating work.

Personally, I fly in my home cockpit and only use the Comanche as that's what it's built for, but that doesn't stop me wanting to see the game improve for others. Your Blackhawk cockpit will not change anything for me, but it will for a lot of other people who like jumping in and out of different choppers.

Please, on behalf of all those others, continue on with your project (no matter how long it takes - you'll get there in the end).

Cheers,

Andy

PS I've been building this cockpit for over 10 years and it's still not finished !!!!!!!!!

Appreciate the comments Andy, but I'm done. Between Banita's negative comments, Reticuli always moaning about things being crap, I just can't be bothered anymore. The code is online for free, someone else can have a go.

At the end of the day, this is a game. I don't need to spend my time on it, especially when most of the feedback is negative. I wanted to get it finished this year, so I could finally walk away from it, but Banita gave me the shove I needed to just let it go.

I've already changed my email to an anonymous protonmail, which has now been deleted, so once I log out, I can't log back in.

I know it looks like spitting the dummy, but trolls win.

Hi Messyhead,

I'm really sorry to see you go mate. You've helped me a lot over the past year.

I can understand how all the negativity could get to you.

As an old fellow engineer one told me :-

Non Iligitimus Carborundumn - "Don't let the #%&*$# get you down".

All the best.

Andy

NICE ONE BANITA !!!!

We've now got one less modder working on the game.

Thanks for that.

Andy