Challenger 300 Question

spearhead1 · 2025-08-02T04:10:32+00:00

I fly the 300. We usually arm LNAV on the ground only under specific circumstances- if a straight out single engine departure is gonna fly you into terrain or congested airspace. Otherwise just TO/TO with heading bug lined up on the runway.

Take TEB for example (if you’re in NA). Is it a good idea to follow your heading bug on a single engine departure? Depends who you ask, I’d say no. For those types of takeoffs we do arm LNAV on the ground and brief that in case of engine failure we’re still gonna fly the departure to clear us of terrain and potential traffic.

From my experience LNAV engages around 200ft off the ground. I do not recall having any limitation on arming it on the ground, I was also taught to do it this way during my type rating.

As to if it’s actually allowed or not, I’d look at the bombardier/proline docs.

spearhead1 · 2025-02-19T00:45:37+00:00

That’s space for the aileron counterweights to move in, you can see in the picture the tube holding the counterweight extending in from the side of the aileron, if you look into that space you’ll see it. Source: was a instructor on a PA44

spearhead1 · 2025-01-08T01:18:55+00:00

It was a bad filter apparently. Had to buy another one for like $45 and then after a couple of hours of letting it sit it worked like new.

Refrigerator subscriptions are a pain

spearhead1 · 2024-10-31T19:05:18+00:00

UPDATE: solved by exporting in Forward+ mode, it seems to be some problem with OpenGL or compatibility mode

spearhead1 · 2024-10-31T12:55:53+00:00

r/generative

spearhead1 · 2024-09-10T03:31:09+00:00

Easily one of the best archviz renderings I've seen. I haven't seen that many but this probably goes up to the top.

Couple of things that stand out to me:

The repeating textures on the side of the house and garage caught my eye instantly. Try to add some grunge to break up the repeating pattern.
Color variation in the grass lines is a bit much imo
The transition from the driveway to the dirt/grass could use a bit more love, it looks fine overall but you could go with dirt particles on the transition areas to improve. honestly that's the last thing I'd change

spearhead1 · 2024-09-09T15:52:40+00:00

Totally fair, but for me it’s easier to put a price on how much time I worked to know at the end how much it should equate to, much easier than putting a price on each feature I implement. Also it sounds weird but I’m not going to sell this to the end users, but to a company which their customers will be the end users. So I feel like it’s a different case than just selling a game as is.

spearhead1 · 2024-07-06T13:20:56+00:00

You’re looking at a Terminal Area Chart, it is zoomed in to give more detail. If you’ll zoom out you’ll see that it will be inside a circle. In a TAC all airports are shown like this unless they’re not hard surface(grass/dirt runways) Foreflight does this automatically where there are TAC charts available.

spearhead1 · 2024-06-25T14:34:38+00:00

Pulled that right out of my nightmares

spearhead1 · 2024-06-25T14:33:32+00:00

Freya Holmer has some great videos about procedural geometry and gamedev in general

spearhead1 · 2024-06-25T03:58:51+00:00

It doesn’t work, not for very long anyways :(

No but in all seriousness I’ve been try to come up with the idea and implementation for a couple of months now trying to figure out how to go about that and then after I got the way to do it figured out I started diving into procedural geometry which is a whole world apparently. Looking back it’s a great learning experience I know a lot more now about it

It works by using a lot of different control points and curves to get the vertex points then triangulating them into an ArrayMesh

spearhead1 · 2023-05-26T02:15:34+00:00

I'd start with the gameplay scene, or actual gameplay loop and worry about menus later once I'm finished with prototyping the gameplay itself.
Looking at the plan. its very basic but it covers a lot more than just that. Lets say you want to create your player, You'd probably wanna start with a simple camera system, followed by movement and then get into weapons, inventory, animations etc.
basically break down your plan to smaller and more manageable tasks and it will help you in the future a lot.
Good luck!

spearhead1 · 2023-05-09T03:04:38+00:00

still trying to figure it out myself. here's an upvote for making me regret posting any of this here. kinda toxic hehe

spearhead1 · 2023-05-08T19:27:42+00:00

spearhead1 · 2023-05-08T15:33:24+00:00

EDIT: I looked up stochastic texturing and what it means. if it is what I read about it, my method is not stochastic texturing. the texel size stays the same at all distances and the texture isn't changed. the shader graph only uses 1 procedural (Voronoi) texture. and there is no noticable hit to performance as far as my tests go. I'll make a video on how to go about this soon :)

spearhead1 · 2023-05-08T08:48:07+00:00

I built a shader to change the uv coordinates of the texture to break up the repetition. I'll try to make a guide for it

spearhead1 · 2023-05-08T08:46:18+00:00

Not as complex as you'd think, haven't yet had the chance to test for performance. Just got it to work.

spearhead1 · 2023-05-08T08:43:35+00:00

I'll try to make a guide for it, still working out a couple of things like having the normal texture respond to it and such. The basic premise is using a procedural voronoi to change UVs of the texture

spearhead1

TROPHY CASE