CCIP Cockpit Mod
-
Hello, I just like to post a big support to my friend Chuck for his great work!
チャックくんがんばれ!
-
If you guys going to post such pictures, I will stop releasing my work for public.
I’m making this mod for myself. I will not hesitate for doing that.While I understand your point of view and respect it, there is a huge contradiction in there
Further I feel threats like this are not necessary. You act as you see fit.
There is no need to make such “kindergarden” threats in advance -
@Red:
While I understand your point of view and respect it, there is a huge contradiction in there
Further I feel threats like this are not necessary. You act as you see fit.
There is no need to make such “kindergarden” threats in advanceYeah, maybe your are right.
There’s a word called “Osusowake” in Japanese language.
It means that, “I made(got) this for myself(my family), but I(we) kindly share this for you.”
It also means that “It wasn’t made for you. I can’t guarantee the quality. So, please don’t complain to me.”The word exactly explains my mind.
So, if people make me uncomfortable by their unrealistic(of course, in my pointview!) modified cockpit, I have no reason to release my work anymore. -
I fully agree and understand and i do the same
But we need to realize that you will always hear the bad things or the peculiar things, but you will never hear (or hardly) from the majority of users who are happy with your work as you released it.
That majority is silent and way more important than the few guys that are complaining or constantly asking for more without even realising the whishes or the method of the author.So as someone sharing it’s work (of love) never be put away by a voicing minority. for every guy complaining about details, there is a hundreth guys being silent but enjoying the work provided.
Think of these guys first and the frustration goes away -
Yeah, maybe your are right.
There’s a word called “Osusowake” in Japanese language.
It means that, “I made(got) this for myself(my family), but I(we) kindly share this for you.”
It also means that “It wasn’t made for you. I can’t guarantee the quality. So, please don’t complain to me.”The word exactly explains my mind.
So, if people make me uncomfortable by their unrealistic(of course, in my pointview!) modified cockpit, I have no reason to release my work anymore.Hi,
I understand how you feel and from a dev POV, maybe these unwritten “rules” will help you manage:
1. Once you release something in Falcon land - Always be sure to grow a thick skin because there will ALWAYS be complains.
2. If someone keeps harassing you on the forums after you explained once (And once is enough!), then just ignore him.
3. 1 or 2 folks out of many that complain/harass/whatever aren’t worth ruining your mood or motivation towards releasing good stuff for everyone else.
4. This isn’t a real job, so never feel rush to do things now. Even if there is a real issue with your work, you can say that you are aware and you will fix whenever you feel up to it.
Follow these “rules” and you will have much happier time with managing your work. FWIW I see complains about my work almost every day, someone says he can’t understand A or can’t find B or why I didn’t implemented C because it’s in the real F-16 since dozen years ago… What I do is I simply read and take notes for myself for what is important, what I may fix and what unlikely, that’s all. I don’t feel like I need to fix anything now nor I have to answer anyone right now. It is what it is.
And last but not least, the most important rule is the mother of all rules:
We are all here for the fun, so let’s just try to enjoy.Cheers!
-
@Red:
I fully agree and understand and i do the same
But we need to realize that you will always hear the bad things or the peculiar things, but you will never hear (or hardly) from the majority of users who are happy with your work as you released it.
That majority is silent and way more important than the few guys that are complaining or constantly asking for more without even realising the whishes or the method of the author.So as someone sharing it’s work (of love) never be put away by a voicing minority. for every guy complaining about details, there is a hundreth guys being silent but enjoying the work provided.
Think of these guys first and the frustration goes awayYeah, that’s totally right.
Unfortunately, I’m aware that I’m narrow minded. -
Hi,
I understand how you feel and from a dev POV, maybe these unwritten “rules” will help you manage:
1. Once you release something in Falcon land - Always be sure to grow a thick skin because there will ALWAYS be complains.
2. If someone keeps harassing you on the forums after you explained once (And once is enough!), then just ignore him.
3. 1 or 2 folks out of many that complain/harass/whatever aren’t worth ruining your mood or motivation towards releasing good stuff for everyone else.
4. This isn’t a real job, so never feel rush to do things now. Even if there is a real issue with your work, you can say that you are aware and you will fix whenever you feel up to it.
Follow these “rules” and you will have much happier time with managing your work. FWIW I see complains about my work almost every day, someone says he can’t understand A or can’t find B or why I didn’t implemented C because it’s in the real F-16 since dozen years ago… What I do is I simply read and take notes for myself for what is important, what I may fix and what unlikely, that’s all. I don’t feel like I need to fix anything now nor I have to answer anyone right now. It is what it is.
And last but not least, the most important rule is the mother of all rules:
We are all here for the fun, so let’s just try to enjoy.Cheers!
Thank you for the good advice, I-Hawk.
I will keep your words in mind. -
Did anyone said harassment? :rofl:
-
FWIW, I have enjoyed following your progress in this thread and I thank you for making it available.
-
Same here thank you Chuck!
-
Hey Chuck great job, keep it up !
But i have to report an issue about F-ACK. It doesn’t work, i tried to test it couple times with different faults but it’s not working for me. The F-ACK screen is blank for all the time.
Btw just wondering about digital altimeter is it WIP or not?
Thanks again for your great job !
(NO PERSONAL MODIFICATIONS)
Best Regards! -
Hey Chuck great job, keep it up !
But i have to report an issue about F-ACK. It doesn’t work, i tried to test it couple times with different faults but it’s not working for me. The F-ACK screen is blank for all the time.
Btw just wondering about digital altimeter is it WIP or not?
Thanks again for your great job !
(NO PERSONAL MODIFICATIONS)
Best Regards!PFD is working correctly in the latest version of release. I confirmed it.
If you mean the altimeter can be found in HAF Vipers, I have no plan to make it.
Because, AFAIK, USAF Block 50 doesn’t have it so far.
But please let me know, if I’m wrong. -
PFD is working correctly in the latest version of release. I confirmed it.
If you mean the altimeter can be found in HAF Vipers, I have no plan to make it.
Because, AFAIK, USAF Block 50 doesn’t have it so far.
But please let me know, if I’m wrong.I just asked for information to a real F16 avionic technician, he will reply to me in couple days. Thanks !
-
This post is deleted! -
Excellent work Peca_Chuck!
Lets make the majority to be loud and heard! -
Hey PeCa, here is a Turkish Air Force F16 Block50-D’s Front Seat Cockpit.
As you can see it has a digital altimeter. I dont have any idea about F16-C but if it will provide a “digital altimer update” to us i can ask for F16-C Block50 photos ?
Edit: Digital altimer confirmed for F16C Block-50 -
Same apply for HAF Block 52’s and Polish Vipers.
-
Installed it a couple weeks ago. Beautiful work Peca Chuck. The attention to detail on the canopy alone is impressive.
-
Hey PeCa, here is a Turkish Air Force F16 Block50-D’s Front Seat Cockpit. http://i.hizliresim.com/r6gX2m.jpg
As you can see it has a digital altimeter. I dont have any idea about F16-C but if it will provide a “digital altimer update” to us i can ask for F16-C Block50 photos ?
Edit: Digital altimer confirmed for F16C Block-50Same apply for HAF Block 52’s and Polish Vipers.
I think his goal is to replicate the USAF Block 50s . Those still have the analog altimeters.
Regards
-
Since I’ve noticed that non-linear output for DOFs is available in 3dckpit.dat, been working on it to get correct indication in some analog instruments.
The problem I have now is, we(end user) cannot have raw data of flight and engine status, except the data in info bar of external view.
That makes nearly impossible to make correct indication in some instrument, even after BMS team incorporated the non-linear DOF schedule.I’ve searched on this forum, .key files and Falcon BMS.cfg to get the kinda “Debug Mode”, but couldn’t find it.
If such “Debug Mod”, which could output or display raw flight/engine data, exists in somewhere, I really want it.
We need it, especially for non-dev side 3d cockpit developer, including me.Please consider my request seriously, DEV team.
If we already have a way to get such data, please let me know.Moreover, would you provide us the specification of non-linear schedule output, if it’s available.
I mean the list of xxx-needle style definition names and corresponded values.
The list will be very useful for 3d cockpit developers.
I will much appreciate for it.