DC Designs F-15 in p3Dv5, no engine sounds at all.
-
For all others, not figuring it out like Rob only thinking for himself, there is a mistake in sound.cfg of DCD F-15 E_I Eagles.
In the sound.cfg of this plane, the alias reference is wrong:
instead of
[fltsim]
alias=DCD F-15 C Eagle\soundthere should be
[fltsim]
alias=DCD F-15 C_D Eagles\soundI bought the plane yesterday at Simmarket "Install_DCD_F15_Eagles_64_TP_103.exe". Unbelievable that such an obvious bug is still there after 9 months beeing available there and a year here at Justflight.
Dan
-
Not aware anyone has reported it as a bug.
-
@Derek
What do you want to say with that?
I hope, it is reported as a bug now.Dan
-
I want to say that I am not aware anyone has raised a ticket with JF support. We don't do support via forums. The OP posted that there were no engine sounds - given the number of copies of the software out there, I think if the engine sounds were missing this would have come to light by now. The OP was from December last year. So, no, this is not something we are currently looking into.
I wonder if Simmarket has the latest version of the code?
There is a list of the update changes here and no mention of the sounds being in the wrong place:
https://support.justflight.com/support/solutions/articles/17000105157-f-15-eagle-changelog
I will mention it to the developer.
-
@Blaunarwal Thanks for highlighting this - I've checked here with the base files and everything seems normal, with the sound folders pointing in the right place. I also have had no reports of this so I wonder if there is somehow something that's been altered in the Sim Market version?
Either way we'll track it down and sort it.
-
Hey guys sorry I didn't put in what I did to solve my issue, I guess I should have posted what happened. I just happened by the forums again tonight to check on Traffic Global.
It turns out that when I installed an app that is part of the Envshade/Envtex family called Envsound (it's an environment sound enhancement thing) it somehow borked the sound of the jet. NOT sure how, I'm not a code guy, but once I replaced the default sound file in P3D (don't ask) it finally worked again.
To get rid of this app I actually had to reinstall P3D, simply removing and reinstalling the F-15 itself didn't work, again, I have no idea why.
Sorry for not letting you guys know, I didn't get a notification to this post, or I would have responded sooner.
-
@RobCom Don´t worry, I thought you are a crack and don´t let us know, how you solved the problem. Your theory about Envsound is only based on the fact it makes sound too. That doesn´t mean it alters files of aircraft simobjects.
-
Not sure what you are saying here, but, just to be clear, no-one has reported an issue with the sounds in the F-15 to us. If your sounds aren't working you should contact Just Flight support.
-
@Derek There´s no need to chime in here, since I wrote to @RobCom and you tell it yourself, you don´t understand what is said here.
No one reported, does not mean no one has a problem. It only means no one reported. And I´m not no one and RobCom is also one. That makes two according to my calculation. I know, this is still nothing for you, because only tickets count and two tickets is also nothing, since you sold about 1000000 F-15s by now and noone else ever had a problem. I solved my problem and I wanted to share the solution, in case there´s one little user out there having the same.
Thanks for your time, your endless effort to help people and to hold the reputation of Justflight high. You´re my absolute hero. -
All very commendable and public spirited, but...
a) From what you have written above, the problem you have had wasn't caused by Envsound. So, you and Rob didn't have the same problem.
b) The 'obvious bug' doesn't appear to be a bug and so it is hard to explain why your fix would be required. Not sure if it would have fixed Rob's problem, because there appear to be two different solutions. It seems more than likely that something (Envsound? Some other program?) may have caused an issue. It would be good to get to the bottom of what that was and provide a fix or an FAQ, rather than require people to tinker with their .cfg files. There really should be no need for that.This is why we don't do support via forums - the solutions offered may sometimes be a hindrance rather than a help.
