-
Posts
134 -
Joined
-
Last visited
Posts posted by sbobovyc
-
-
@Lucky StrikeAmazing work. I hope to get to porting the Blender plugins to 2.80 around Christmas. The metadata is editable from Blender and I will rely on the community to figure it out and tell me.
-
Just happened to see a newsletter from Matrix games about this. Congratulations to Battlefront and I hope it leads to bigger things in the future!
-
I am slowly porting the Blender plugin to 2.80. There were substantial changes to the API and I have a lot less free time these days, so it will take a while.
-
Blender 2.80 removed the internal rendered, so you will now have to learn about BSDF and node based shading
-
-
In my experience, skinned meshes take a substantial amount of time to reverse engineer. Adding to the difficulty, CM does the animation on the CPU side instead of in the GPU shader which makes this even more involved. It may be that I never get around to it.
-
From user reports and my reading of the Blender 2.8 API, the Blender plugins will not work on 2.8. It will be sometime before I port the tools, so for the near future Blender 2.79 is the latest version that is supported.
-
To get started with texture mapping in Blender, checkout the "UV Editing" view in blender. You can change your views by clicking on the left drop down in the (1) box.
-
@Aquila-CM We are going to have to sit down one day on Teamviewer and get to the bottom of this problem you encounter with deleting faces.
-
Aquila-CM's excellent work motivated me to release the metadata update. The infantry file format is different than static objects, and though I made some progress reverse engineering it I would like to finish up mdr first.
-
@The Steppenwulf I did some experimentation, but I don't have anything conclusive. One of these days I will get all my notes together and put them out, but for now it's best for people to experiment and share what they find. The meta data is the key to getting custom vehicles fully working since it contains data for wheels and suspensions.
-
New version 0.9.2 of the Blender tools has been released. The importer/exporter now support what I call "metadata". For example, import bush1.mdr from CMSF2 with the meta data import enabled and you will see that the "trunk" object has custom properties.
-
I am glad the tools are getting some use. Been really busy with real life stuff, so I never got around to figuring out how vehicles work. For the more advance users of Blender, you can import what I call "metadata" by checking a box in the importer. The data will show up in the object tab, under "Custom Properties." You can tweak things and when exporting the model also export the metadata. For example, I deleted the UAZ's canvas cover and had a fully working vehicle. The metadata could also be edited and exported, facilitating reverse engineering of its meaning.
-
Good call, the previous save games are in the hundreds of KB.
-
Both players are using v2.01, no mods.
https://drive.google.com/open?id=1FIXyIXY1t0OsY4v1oBgbQX-8sD6zqfV6
-
Is it like the banding on the roof that I captured here?
-
-
I will try to take a look this weekend.
-
-
-
Here is the backtrace of my crash:
00481248 mov eax,dword ptr [edi+10h]
0048124B mov ecx,dword ptr [eax]
0048124D lea eax,[edi+1Ch]
00481250 push eax
00481251 push dword ptr [ebp+8]
00481254 mov edx,dword ptr [ecx]> CM Shock Force 2 Demo.exe!00481254() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for CM Shock Force 2 Demo.exe]
CM Shock Force 2 Demo.exe!0048628e() Unknown
CM Shock Force 2 Demo.exe!00482270() Unknown
CM Shock Force 2 Demo.exe!006de308() Unknown
CM Shock Force 2 Demo.exe!006de4b7() Unknown
[External Code]
CM Shock Force 2 Demo.exe!005302b1() Unknown
[External Code]
CM Shock Force 2 Demo.exe!005308bb() Unknown
[External Code]EAX 2E6FB984
ECX 00000001
EDX 00000000
EBP 0018FBBC
EDI 2E6FB968 -
Crash on demo at Alamo, Win 7 64 bit. I have a save that can repro the crash.
-
Looks like the "inside" object is clipping through the marder hull.
-
1 hour ago, Bulletpoint said:
I don't think it's the shot calculations that eat up much computation time actually. I don't see any slowdown even in the moments when there's hundreds of bullets flying at the same time.
But in situations without any firing, scrolling around over a map feels sluggish to me, even when reported framerates are at a level that should be reasonable, around 30 FPS. It doesn't seem like normal low FPS lag like in other games I played. More of a "stuck in molasses then sliding on ice" kind of feel.. if that makes sense
You are probably experiencing stuttering due to the rendering scene complexity. Trees are a bad culprit since each one is rendered separately. Each tree takes a few function calls (too lazy to give you an exact number) to render. It's not a problem if you are rendering a few, but it adds up quickly when you have to render 50.
AMD 22.8 series breaks game again
in CM2 General Tech Support
Posted
I can confirm this. After upgrading to 22.8.2, game UI and rendering are broken.